No database in minidlna after update FW / spd8020 to 15.0

[tom2005]

Hi Jocko

thank you for your assistance.
I am not familiar with putty at the Moment.

So I did the Action requested on the Web Console:
- Clock adjusted
6. Page - FTP Server
- mark Server set active removed - saved
- mark Server set active set - saved

Here is the result:

Nov 16 12:54:21 SPD8020-7EBBB4.local proftpd[1124] 127.0.0.1: ProFTPD 1.3.4a (maint) (built Thu Feb 9 2012 21:19:20 GMT+1) standalone mode STARTUP
Oct 24 23:38:28 SPD8020-7EBBB4.local proftpd[1321] 127.0.0.1 (192.168.1.28[192.168.1.28]): FTP session opened.
Oct 24 23:38:30 SPD8020-7EBBB4.local proftpd[1321] 127.0.0.1 (192.168.1.28[192.168.1.28]): Preparing to chroot to directory '/share/1000/fvdw'
Oct 24 23:38:30 SPD8020-7EBBB4.local proftpd[1321] 127.0.0.1 (192.168.1.28[192.168.1.28]): USER fvdw: Login successful.
Oct 24 23:38:35 SPD8020-7EBBB4.local proftpd[1321] 127.0.0.1 (192.168.1.28[192.168.1.28]): FTP session closed.

Tom

[Jocko]

:thumbup
So I assume that now the ftp server is still running ?(see the main Information menu)
If it's ok test if you can access with the other share.

But why FTP failed to start when the NAS was booting :scratch

[tom2005]

Hi Jocko,

do you know where the config is saved?
Is a battery involved.

Just I have performed the restart and there after the shutdown.
Both times the FTP is running, but the correction for the time Settings are lost now.
All Shares has been connected successful.

Good night for now and thank you

Tom

[Jocko]

Tom2005,

what config do you talk ? FTP or time settings ?

For the server FTP, the conf file (/etc/proftpd.conf) is overwritten at each boot according with NAS database.

About time settings and the lost correction after booting.
I assumed that you don't use ntp servers and indeed in this case there is an issue. This bug is now fixed and version 15.1 will include the patch.

Be aware that without ntp server, the local time is restored at booting by using the CPU time and it can have a deviation. We did not include a feature to correct this deviation because the use of ntp servers is easy and effecient.

[tom2005]

Good morning Jocko,

Tom2005,

what config do you talk ? FTP or time settings ?

I was thinking about if the config is saved in a battery buffered aeria and this is going empty?

under post 14 I wrote:

Edit: something is wrong with the time Settings.
2 german timeserver are in use 192.53.103.103 / 104 PTB Braunschweig.

The MiniDlna Log listed the following lines. You can see the step back to 2011 after power down.
Is this a know Problem? I have seen it since the Update in Dec. 2012.

Today the FTP is still running after power down, but the Minidlna everytimes turns off by itself on the web indication but it is still working with the TV´s.

Tom

[Jocko]

I was thinking about if the config is saved in a battery buffered aeria and this is going empty?

No there is no battery involved. The firmware saves the settings in a database file and at booting it restores the configuration

Edit: something is wrong with the time Settings.
2 german timeserver are in use 192.53.103.103 / 104 PTB Braunschweig.

So you use these servers : ptbtime2 and ptbtime3.

I note that the stratum of these servers is 1. You don't need to use this stratum level. Usually these servers are available only after a request and if you send too many synchronizations, your IP can be banned by the NTP server's administrator.

I read also about the ptbtimeX.ptb.de server

Um die Zeitserver der PTB zur Synchronisation eines Rechners nutzen zu können, wird ein Programm benötigt, das dieses Protokoll unterstützt. Für die Betriebssysteme Windows, UNIX, Macintosh u.a. sind derartige Programme verfügbar.

A not standard protocol is required for these servers which is not implemented in our firmware...

So you have to use other ntp servers. (See this German list : http://www.hullen.de/helmut/filebox/DCF77/ntpsrvr.html). a Stratum level 3 is enough (but stratum 2 can also be used). You must check also if the NTP server's administrator asks you for a prior permission.

About MiniDlna fvdw knows better this server to make a respond

[tom2005]

Hi Jocko,

It is done and the time indication is correct now.

Thank you for the first part

[Jocko]

About Minidlna,

I quickly looked how the firmware checks if the server is running.

The firmware assumes that the server is running if it finds the pid file /var/run/minidlna.pid. But this path uses a symlink: so maybe there is an issue with it or the firmware fails to create it when it starts minidlna and then maybe there is a permissions issue.

To check this you must use Putty :whistle

After logging do these commands

Code: Select all

 ls -al /var/run

Code: Select all

ls -ld /rw_fs/tmp/var/run

and

Code: Select all

ls -l /rw_fs/tmp/var/run/minidlna.pid

[tom2005]

Hi Jocko,
this is the answer I get

login as: root
root@192.168.1.3's password:
root@SPD8020-7EBBB4:/ # ls -al /var/run
lrwxrwxrwx 1 root root 18 2011-11-16 12:00 /var/run -> /rw_fs/tmp/var/run
root@SPD8020-7EBBB4:/ # ls -ld /rw_fs/tmp/var/run
drwxrwxrwx 4 nobody nobody 1024 2011-11-16 12:02 /rw_fs/tmp/var/run
root@SPD8020-7EBBB4:/ # ls -l /rw_fs/tmp/var/run/minidlna.pid
ls: /rw_fs/tmp/var/run/minidlna.pid: No such file or directory
root@SPD8020-7EBBB4:/ #

and now?

Thanks for further assistance

Tom

[Jocko]

Thank Tom2005

Now we know why minidlna is declared as not running by the web interface : the pid file is missing

But I forgot two others commands to check if minidlna is really running

Code: Select all

ps -ef|grep minidlna|grep -v grep

and

Code: Select all

netstat -apW|grep minidlna

Otherwise do also this command

Code: Select all

df -h /dev/sda5