Turris OS 3.10.3 released

release

#22

Is there any other tip or advice what to do with this issue?
Please try to help me.

(After update to 3.10.3 pakon stopped to work.
I have tried to tips already available in forum such as py script to create database,reinstall and restarts,but nothing helped.)

I did not deleted any file. And this did not help:
/usr/libexec/pakon-light/create_db.py


#23

@xjerab08 I’m not sure if reinstalling pakon or running create_db.py will truly recreate the database if there are already existing database files. Since you were ok wiping out any existing pakon data anyway, try this:

Stop the pakon processes:

/etc/init.d/pakon-handler stop
/etc/init.d/pakon-monitor stop

Remove all extant pakon DB files, then recreate the DB (assuming you have the database files at the default places. /var/lib/pakon.db is the active db file in RAM, while /srv/pakon contains the DB backed up in persistent storage (one compressed DB file with the last 24 hours of data, updated once every 8 hours called pakon.db.xz, and another archive DB with all data older than 24 hours, called pakon-archive.db)

rm /var/lib/pakon.db
rm /srv/pakon/*
/usr/libexec/pakon-light/create_db.py

Then restart pakon:

/etc/init.d/pakon-monitor start
/etc/init.d/pakon-handler start

From my experiments pakon should be starting out with a completely clean slate this way.


Pakon-monitor stops running
New device in LAN - alert
#24

As with the previous version I’m (not alone) experiencing issue Mountd spamming the system log about missing sda serial.

2018-07-05 12:06:01 crit mountd[7598]: could not find a serial number for the device sdb
2018-07-05 12:06:06 crit mountd[23603]: Last message 'could not find a ser' repeated 9 times, suppressed by syslog-ng on turris
2018-07-05 12:06:06 crit mountd[7598]: could not find a serial number for the device sdb
2018-07-05 12:06:11 crit mountd[23603]: Last message 'could not find a ser' repeated 9 times, suppressed by syslog-ng on turris

That’s 2 messages per every second.
Please advise.


#25

Was it necessary to post 3 posts about this issue? This doesn’t make anything better. The forum should be organized.
We know about your thread, but I couldn’t reproduce it, yet.
In recent days we received from other users that it is happening to them, too. Sometimes things require time to track them down and fix them.


#26

Maybe a little notice from you in the thread would make us all a little more comfortable knowing Turris Team cares and would prevent me from desperate measures. :wink:
Actually it had me post these 3 messages to know what I know now from your reply.
Thank you.


#27

This actually helped! Thank you.


#28

Cross-ref: CIFS suddenly agonizingly slow (apparently caused by the .3 bump)


#29