sem_ errors

[QuaCKeReD]

Hi All,

Am pretty new to Zabbix, but loving its capability.

I am using RaspberryPi as server, and have run tests with both MySQL and SQLite3 databases - due to resource limitations of RPi, and the fact I only have about 10 devices to monitor, I have chosen to go with SQLite3.

Now, onto my issue;

I can install and setup Zabbix 2.0.3, no problems; compiling from source. And the web interface works fine.

However, after a reboot, everything goes to pot!

Web Page shows following error on login screen;

sem_release() expects parameter 1 to be resource, boolean given [include / db.inc.php:1161]

and gets worse after logon - with these errors in every 'box';

sem_get(): failed for key 0x7a0212a6: Permission denied [include / db.inc.php:1139]
sem_acquire() expects parameter 1 to be resource, boolean given [include / db.inc.php:1150]
sem_release() expects parameter 1 to be resource, boolean given [include / db.inc.php:1161]
...
sem_acquire() expects parameter 1 to be resource, boolean given [include / db.inc.php:1150]
sem_release() expects parameter 1 to be resource, boolean given [include / db.inc.php:1161]

The file mentioned is located at /var/www/include, and looks like this;
-rw-r--r-- 1 root root 29676 Oct 3 15:41 db.inc.php

Apache is running as normal, first process as root, spawn processes as www-data

Both zabbix_server & zabbix_agentd are running as zabbix user

SQLite3 DB is located in /home/zabbix/zabbix.db, with zabbix folder and file at zabbix:zabbix and 777


I have reinstalled 3 times now, and each time, it works until a reboot.

Any ideas?

[QuaCKeReD]

Have checked zabbix log - nothing

Apache log shows following;

[Tue Oct 16 22:43:14 2012] [error] [client 192.168.5.15] PHP Fatal error: Call to a member function fetchArray() on a non-object in /var/www/include/db.inc.php on line 601, referer: http://192.168.5.120/dashboard.php

[stepw]

Looks like zabbix-server locks DB file exclusively without creating a semaphore when it starts. Consequently if frontend is trying to access DB file while server process is already running, it fails and the error message in question comes up.

If the server process is stopped, frontend comes up without errors. Furthemore, if server process is later started again, DB locking seems to work for both... to some extent. Frontend still spits up sqlite3 related errors often due to DB locking by server process.

sqlite support is still considered experimental and it might never be mature enough for real life use.

Maybe you can squeeze mysql in by reducing memory consumption, see, for example http://www.lowendbox.com/blog/reduci...low-end-boxes/