Input's updates, the feeds do not

boelle · 2019-05-05T10:42:33.673Z

where is the settings.php located?

borpin · 2019-05-05T10:44:59.397Z

root emoncms folder

pb66 · 2019-05-05T10:47:53.305Z

borpin:

Almost certainly /log/var filling up.

Whooooaa! That’s a huge step!

Firstly this is an early image (emonSD-26Oct17) so we don’t even know if the changes that cause the logs to fill up are present.

Secondly, i think Redis needs checking

image878×658 52.8 KB

I would expect some redis keys to have been created in the 30mins runtime (has this value changed in the admin screen?)

From the update script

setup logrotate state & logfile in /var/log/logrotate
mkdir: cannot create directory ‘/var/log/logrotate’: File exists

Completed

Running logrotate...

set log rotate config owner to root
chown: changing ownership of ‘/etc/logrotate.conf’: Read-only file system

now this might not be all bad as the logrotate used to work (or sort of) and it’s the recent breakage combined with the changes to the emonhub systemd file that have caused the logs to fill up.

   tmpfs            50M  520K   50M   2% /var/log
does not look full to me, or am i wrong?

How long has it been running at this point? When was it last rebooted?

Even if the logs were not filling up before, they might now you have updated.

borpin:

The fix, as it stands, doesn’t work IMNSHO.

That’s because the “quick” fix for this issue in the current updater is to revert emonhub logging to emonhub.log (not via stdout and journald) and to sure up the logrotation again. We need to undo the breakages rather than slapping on more sticking plasters.

boelle · 2019-05-05T10:49:02.097Z

pb66:

Firstly this is an early image (emonSD-26Oct17)

but fully updated from within emoncms

borpin · 2019-05-05T10:49:08.856Z

pb66:

Whooooaa! That’s a huge step!

yes I know - self hosted.

boelle · 2019-05-05T10:50:47.159Z

pb66:

I would expect some redis keys to have been created in the 30mins runtime (has this value changed in the admin screen?)

Redis	Version	2.8.17
	Host	localhost:6379 (127.0.0.1)
	Size	76 keys (560.60K)

boelle · 2019-05-05T10:51:36.328Z

pb66:

Whooooaa! That’s a huge step!

in first post:

this is a SELFHOSTED install of emoncms

boelle · 2019-05-05T10:52:33.068Z

pb66:

How long has it been running at this point? When was it last rebooted?

multiple reboots during last hour (or was it last half hour

boelle · 2019-05-05T10:55:07.762Z

pb66:

Even if the logs were not filling up before, they might now you have updated.

i do not interrupt my sleep 2:00 in the morning to do upates
so i would say no to updates being at fault, and even if they are logs should not be filling up
if they did openenergy would suddenly have customers complaing about the units they sell do not work as they should

boelle · 2019-05-05T10:57:13.555Z

sorry for the multiple posts but i had to break it down in to bits i could figure and manage

is there more i can test etc?

borpin · 2019-05-05T10:58:09.641Z

Have you changed the logging level? You should see more entries in the admin page.

boelle · 2019-05-05T10:58:43.097Z

yep… i get a lot of

2019-05-05 10:58:01.430|INFO|index.php|admin/getlog

will have to find where it gets data in… hold on

boelle · 2019-05-05T10:59:19.355Z

got this

pb66 · 2019-05-05T10:59:27.378Z

boelle:

this is a SELFHOSTED install of emoncms

borpin:

yes I know - self hosted

??? All emonPi/base/SD’s are self-hosted, why are you shouting @boelle?

Do we all mean self built?

As it must be an emonSD image since it returns the image version and the updater mostly works!

boelle:

i do not interrupt my sleep 2:00 in the morning to do upates
so i would say no to updates being at fault, and even if they are logs should not be filling up

I didn’t suggest you did! That’s why I said the log filling up was less likely

I did however assume you might have tried updating since then, because that’s what most users would do when they have a problem. Update to ensure any known issues that are fixed are eliminated!

boelle · 2019-05-05T11:00:05.270Z

got one

2019-05-05 10:59:47.092|INFO|emoncms_mqtt.php|0 Messages processed in last 5 minutes

boelle · 2019-05-05T11:02:08.668Z

oki, will update all and reboot

boelle · 2019-05-05T11:02:50.488Z

before that here is a copy of log

LAST ENTRIES ON THE LOG FILE

boelle · 2019-05-05T11:08:06.693Z

while it updates

is this PR related? WIP Better method to create tmpfs /var/log files on startup by glynhudson · Pull Request #81 · openenergymonitor/emonpi · GitHub

pb66 · 2019-05-05T11:13:03.976Z

boelle:

is this PR related?

No. That was something Glyn was toying with but didn’t reach release.

boelle · 2019-05-05T11:18:17.219Z

updated and rebooted

one of the 2 feeds is updated but not at the 60 sec interval it should