Ticket #2831 (closed defect: worksforme)
problem when quering logs
| Reported by: | forumail2@… | Owned by: | jacalvo@… |
|---|---|---|---|
| Milestone: | Component: | base | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
The problem comes when i try to query logs. Every log(http proxy,firewall, etc). The technical details are in the photo below and i also include the log file
Attachments
Change History
comment:1 follow-up: ↓ 2 Changed 2 years ago by jacalvo@…
- Status changed from new to closed
- Resolution set to worksforme
It seems a problem with your postgresql daemon. Could you try to execute "/etc/init.d/postgresql-8.4 restart"?
Did this suddenly stop working or is it failing since the beginning of a fresh installation?
We would need more information in order to try to reproduce it.
comment:2 in reply to: ↑ 1 Changed 2 years ago by forumail2@…
- Status changed from closed to reopened
- Resolution worksforme deleted
Replying to jacalvo@…:
It seems a problem with your postgresql daemon. Could you try to execute "/etc/init.d/postgresql-8.4 restart"?
Did this suddenly stop working or is it failing since the beginning of a fresh installation?
We would need more information in order to try to reproduce it.
The output of the above command is this:
Restarting PostgreSQL 8.4 database server The PostgreSQL server failed to start. Please check the log output: FATAL: invalid value for parameter "lc_messages": "en_US.UTF-8"
where is the log output if u need it?
It started suddenly!
comment:3 follow-up: ↓ 4 Changed 2 years ago by jacalvo@…
Have you recently changed anything related with language/locales on your system?
comment:4 in reply to: ↑ 3 Changed 2 years ago by forumail2@…
Replying to jacalvo@…:
Have you recently changed anything related with language/locales on your system?
The only thing i did was to remove(for a while) the folder locale from /user/lib64 in order to give some space to my disk.After i gave more space to root partition, i putted the folder again to it's place...
Is it fixable?
comment:5 follow-up: ↓ 6 Changed 2 years ago by jacalvo@…
- Status changed from reopened to closed
- Resolution set to invalid
The error seems related with what you did. If the folder is in place again and has the right permissions you can try to execute "/etc/init.d/postgresql-8.4 stop" and "/etc/init.d/postgresql-8.4 start", or even try to reboot the entire system. Anyway I'm closing this as this does not seem a Zentyal bug.
comment:6 in reply to: ↑ 5 ; follow-up: ↓ 7 Changed 2 years ago by forumail2@…
- Status changed from closed to reopened
- Resolution invalid deleted
Replying to jacalvo@…:
The error seems related with what you did. If the folder is in place again and has the right permissions you can try to execute "/etc/init.d/postgresql-8.4 stop" and "/etc/init.d/postgresql-8.4 start", or even try to reboot the entire system. Anyway I'm closing this as this does not seem a Zentyal bug.
Thnks for all your efforts on helping me ,but even if it is not a zentyal bug(??? isn't it ???) could i ask if i can uninstall the postgresql server and install it back again like the boys did on this http://ubuntuforums.org/showthread.php?t=1405239 ??
comment:7 in reply to: ↑ 6 Changed 2 years ago by forumail2@…
Sorry to reopen but it seems that it wasn't the problem. I was able to restart the postgresql server with success but the problem still occurs.
U might want to take a look at the message below.
Trace
There wasn't a database connection, check if database exists\n at /usr/share/perl5/EBox/PgDBEngine.pm line 139
EBox::PgDBEngine::_disconnect('EBox::PgDBEngine=HASH(0x7fa909cf4fa8)') called at /usr/share/perl5/EBox/PgDBEngine.pm line 665
EBox::PgDBEngine::DESTROY('EBox::PgDBEngine=HASH(0x7fa909cf4fa8)') called at /usr/share/perl5/Error.pm line 408
EBox::CGI::Base::run('EBox::CGI::Logs::Index=HASH(0x7fa904fa6a40)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Logs/Index', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 35
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0x7fa904f09b88)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x7fa904f09f78)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x7fa904f09f78)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0x7fa904f09b88)') called at -e line 0
eval {...} called at -e line 0
comment:8 Changed 2 years ago by jacalvo@…
- Status changed from reopened to closed
- Resolution set to worksforme
Try with /usr/share/ebox/ebox-create-db
But anyway if this was working and stopped to work due to some files you moved I don't think it is a Zentyal bug. Maybe you can ask for help to recover your system at http://forum.zentyal.org, but please do not reopen this unless you are sure this is a bug in the Zentyal code.
