Ticket #2111 (closed defect: worksforme)
Logs not working
| Reported by: | bobthebob1234 | Owned by: | cperez@… |
|---|---|---|---|
| Milestone: | Component: | logs | |
| Severity: | normal | Keywords: | logs, events |
| Cc: |
Description
Whenever I try and view 'Full report' logs in ebox it just says There wasn't a database connection, check if database exists\n and for 'Summarized report' i just get An internal error has occurred. This is most probably a bug, relevant information can be found in the logs.
Attachments
Change History
comment:1 follow-up: ↓ 2 Changed 3 years ago by jsoriano@…
Hi,
Did you have any problem during installation?
Try to reinstall ebox package (sudo apt-get install --reinstall ebox) and tell us if it reports any failure.
Regards.
comment:2 in reply to: ↑ 1 ; follow-up: ↓ 3 Changed 3 years ago by anonymous
Replying to jsoriano@ebox-platform.com:
Hi,
Did you have any problem during installation?
Try to reinstall ebox package (sudo apt-get install --reinstall ebox) and tell us if it reports any failure.
Regards.
I didn't when I originally installed ebox, however I did some updates and it went a bit do lally. I reinstalled at that point with no errors, but i'll do it again.
comment:3 in reply to: ↑ 2 Changed 3 years ago by bobthebob1234
Replying to anonymous:
Replying to jsoriano@ebox-platform.com:
Hi,
Did you have any problem during installation?
Try to reinstall ebox package (sudo apt-get install --reinstall ebox) and tell us if it reports any failure.
Regards.
I didn't when I originally installed ebox, however I did some updates and it went a bit do lally. I reinstalled at that point with no errors, but i'll do it again.
I just reinstalled and no errors came up. However still getting the same error. I also restarted the server just in case. Squid no longer automatically starts and I keep getting 'event already exists.', for example when I try and start 'monitor' or I click on events.
comment:4 Changed 3 years ago by igor@…
I have the same error too. System - Ubuntu 10.04 x86_64. I don't can make system backup and view logs. I install ebox v1.5 2 month ago and yesterday upgrade to 1.5.14 from repo. Ldap server now not start automatic and error about database connection persist.
Trace log:
There wasn't a database connection, check if database exists\n at /usr/share/perl5/EBox/PgDBEngine.pm line 122 EBox::PgDBEngine::_disconnect('EBox::PgDBEngine=HASH(0x7f6c687222c8)') called at /usr/share/perl5/EBox/PgDBEngine.pm line 469 EBox::PgDBEngine::DESTROY('EBox::PgDBEngine=HASH(0x7f6c687222c8)') called at /usr/share/perl5/Error.pm line 408 EBox::CGI::Base::run('EBox::CGI::Logs::Index=HASH(0x7f6c68470128)') called at /usr/share/perl5/EBox/CGI/Run.pm line 122 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(0x7f6c647dcdc0)') 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(0x7f6c647cb998)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170 ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0x7f6c647cb998)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31 ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec?=SCALAR(0x7f6c647dcdc0)') called at -e line 0 eval {...} called at -e line 0

it told me to attach this log file