No disk space although enough room

pi@emonpi:~ $ mysqlcheck --auto-repair -u emoncms -p emoncms
Enter password:
emoncms.app_config                                 OK
emoncms.dashboard                                  OK
emoncms.demandshaper                               OK
emoncms.device                                     OK
emoncms.feeds                                      OK
emoncms.graph                                      OK
emoncms.input                                      OK
emoncms.multigraph                                 OK
emoncms.postprocess                                OK
emoncms.rememberme                                 OK
emoncms.schedule                                   OK
emoncms.setup                                      OK
emoncms.sync                                       OK
emoncms.users                                      OK
pi@emonpi:~ $

when I ran this command this morning, I got the same result as last week, but now it seems to be updated

pi@emonpi:~ $ tail -f /var/log/daemon.log -n 200
Dec 21 17:09:17 emonpi systemd[1]: Starting Clean php session files...
Dec 21 17:09:18 emonpi systemd[1]: phpsessionclean.service: Succeeded.
Dec 21 17:09:18 emonpi systemd[1]: Finished Clean php session files.
Dec 21 17:13:03 emonpi mariadbd[621]: 2022-12-21 17:13:03 6306 [Warning] Access denied for user 'emoncms'@'localhost' (using password: NO)
Dec 21 17:13:31 emonpi mariadbd[621]: 2022-12-21 17:13:31 6307 [Warning] Access denied for user 'emoncms'@'localhost' (using password: YES)
^C
pi@emonpi:~ $

@TrystanLea - these errors anything to worry about?

Hi @VincentR (@TrystanLea)

I’ve had a chance to look at the logrotate errors. Part of the issue is a change to logrotate making 2 of the commands we were using mutually exclusive (reference make `renamecopy` and `copytruncate` override each other by kdudka · Pull Request #386 · logrotate/logrotate · GitHub & logrotate/ChangeLog.md at master · logrotate/logrotate · GitHub)

Firstly have you seen any other problems with log size (I’m expecting you will)

I have modified the logrotate files. If you want to give them a try, I can walk you through the process.

[edit]
Issue

Brian Orpin via OpenEnergyMonitor Community schreef op 2022-12-28 18:47:

| borpin Brian Orpin
28 December |

  • | - |

Hi @VincentR (@TrystanLea)

I’ve had a chance to look at the logrotate errors. Part of the issue is a change to logrotate making 2 of the commands we were using mutually exclusive (reference make renamecopy and copytruncate override each other by kdudka · Pull Request #386 · logrotate/logrotate · GitHub & logrotate/ChangeLog.md at master · logrotate/logrotate · GitHub)

Firstly have you seen any other problems with log size (I’m expecting you will)

I have modified the logrotate files. If you want to give them a try, I can walk you through the process.


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

Hi Brian,

thnx for the determination of this problem, as I’m overasked by this.

As of Christmas I did not take a look at the filesizes anymore (will do when I’m home), but still experienced the troubles with the “inputs” menu.

I’m really interested in the modified files, but not very common to the RPi commandline interface. Never to young to learn, so please guide me through.

Hi Brian, reading your discussion with Alexander on Github I was wondering what to do for me? Can you guide me through the necessary steps?