Hi,

 

Thanks for your reply.

 

I checked the installation folder and compared the access rights to what was in a backup .tar file.

In the tar file it was set as observium:www-data and the actual folder was set to observium:observium.

So that was changed but I can’t remeber doing that. Changed it back but without effect.

 

 

Observium is running as user observium and when switching to that user, I can create a test file in the rrd folder.

So write permission seems ok.

 

 

When I look at the polling information per device it’s not updated since early January.

Manually running the polling.sh script is working fine and I see other updates as system down, rebooted etc.

 

 

The observium.log file is filled with these lines:

 

poller-wrapper.py(2850970): /opt/observium/poller-wrapper.py: ERROR: Could not connect to MySQL database!

 

 

The housekeeping jobs are scheduled as user observium in /etc/cron.d/opbservium.

# Run multithreaded poller wrapper every 5 minutes

*/5 *     * * *   observium    /opt/observium/poller-wrapper.py >> /dev/null 2>&1

 

 

I can connect to the mysql database using the credentials found in config.php as the user observium for which the poller-wrapper.py is scheduled:

 

$ id

uid=1001(observium) gid=1001(observium) groups=1001(observium),33(www-data)

 

$ mysql -uobservium –p********** observium

mysql: [Warning] Using a password on the command line interface can be insecure.

Reading table information for completion of table and column names

You can turn off this feature to get a quicker startup with -A

 

Welcome to the MySQL monitor.  Commands end with ; or \g.

Your MySQL connection id is 41

Server version: 8.0.27-0ubuntu0.20.04.1 (Ubuntu)

 

Copyright (c) 2000, 2021, Oracle and/or its affiliates.

 

Oracle is a registered trademark of Oracle Corporation and/or its

affiliates. Other names may be trademarks of their respective

owners.

 

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

 

mysql> status

--------------

mysql  Ver 8.0.27-0ubuntu0.20.04.1 for Linux on x86_64 ((Ubuntu))

 

Connection id:          41

Current database:       observium

Current user:           observium@localhost

SSL:                    Not in use

Current pager:          stdout

Using outfile:          ''

Using delimiter:        ;

Server version:         8.0.27-0ubuntu0.20.04.1 (Ubuntu)

Protocol version:       10

Connection:             Localhost via UNIX socket

Server characterset:    utf8mb4

Db     characterset:    utf8mb3

Client characterset:    utf8mb4

Conn.  characterset:    utf8mb4

UNIX socket:            /var/run/mysqld/mysqld.sock

Binary data as:         Hexadecimal

Uptime:                 4 min 22 sec

 

 

So why can’t the scheduled job not connect anymore to the mysql database?

 

 

Regards,

Richard

 

 

Van: observium [mailto:observium-bounces@observium.org] Namens Adam Armstrong via observium
Verzonden: maandag 24 januari 2022 13:01
Aan: Observium <observium@observium.org>
CC: Adam Armstrong <adama@observium.org>
Onderwerp: Re: [Observium] All graphs stopped at Jan 1st 00:00

 

++++++ !!! DIT IS EEN EXTERNE E-MAIL: WEES VOORZICHTIG BIJ HET OPENEN VAN LINKS OF BIJLAGEN !!! ++++++

The most likely causes of this are poller not running and permissions.

 

You can check the first one by seeing if non-graph data is being update, and if the device has poll/discovery entries in its pollerlog.

 

The latter one you just need to check permissions on the rrd folder and contents to make sure they’re writeable by the user the poller runs as.

 

Adam.

Sent from my iPhone