Internal Server Error

[GoogleCodeExporter]

Internal Server Error

[GoogleCodeExporter]

I just ran the install on ubuntu 11.10 x64 and I am getting the same error.  
Any help would be appreciated.

Original comment by [email protected] on 26 Jan 2012 at 8:43

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I can confirm the issue on CentOS 6, the database permissions do seem ok.

Original comment by [email protected] on 30 Jan 2012 at 3:48

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I found this to be caused by a missing syslog mysql database. I needed to 
configure rsyslog to log to mysql first and add the mysql user details to 
/etc/elsa_web.conf.

The web-interface still does not show, does not stop loading, but that would be 
a separate issue.

Original comment by [email protected] on 1 Feb 2012 at 2:41

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

This sounds like an error caused by not pointing at a node database or the 
configured username not having access to the node database as per the 
elsa_web.conf file.

Database error reporting to the front-end should be fixed in the current 
version.  Can you please run install.sh again and give it a shot?

Original comment by [email protected] on 2 Feb 2012 at 8:07

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I tried installing ELSA, but the same problem was reached on Ubuntu 10.04 LTS. 
After solving it via elsa_web.conf, I still get problem as described in the 
third comment by [email protected]

Original comment by [email protected] on 10 May 2012 at 4:09

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

For both the meta_db and the node databases under "nodes," are you able to log 
in using the credentials specified in the elsa_web.conf file?  

Original comment by [email protected] on 10 May 2012 at 6:56

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I just installed ELSA for the first time on Ubuntu 12.04 LTS and am seeing the 
same thing.

My Apache error log shows, "Can't use string ("Access denied for user 
'elsa'@'l") as an ARRAY ref while "strict refs" in use at 
/usr/local/elsa/web/lib/API.pm line 705.\n"

The ELSA log is showing, "* ERROR [2012/05/25 20:24:02] 
/usr/local/elsa/web/lib/AsyncMysql.pm (30) AsyncMysql::query 2499 [undef]
Got connection error Access denied for user 'elsa'@'localhost' to database 
'syslog' at /usr/local/elsa/web/lib/AsyncMysql.pm line 26."

I guess I'm having the same situation as comment #3.

Original comment by [email protected] on 26 May 2012 at 3:26

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

So the issue seemed to be that rsyslog's MySQL support module was simply never 
installed with Ubuntu.  Once I added that component and re-ran the installation 
script, things seem to start up fine.

Original comment by [email protected] on 26 May 2012 at 4:27

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Glad you got it working, but I'm confused where rsyslog comes into play.  Can 
you tell me exactly which component you had to add?  Thanks.

Original comment by [email protected] on 29 May 2012 at 2:12

• Added labels: ****
• Removed labels: ****