Another minidlna issue after upgrading from 17.x to 18.2

Another minidlna issue after upgrading from 17.x to 18.2

Postby jpjpjp » Tue Feb 28, 2023 2:26 pm

Hello.

I finally got around to updating my firmware earlier this week using the instructions from Jocko here: viewtopic.php?f=11&t=3678&start=16

A couple of days later I noticed that minidlna wasn't running. When I logged in to the webconsole it says "Server is not installed". When I click the "Install Server" button I get "Fail: install command failed (17)"


When I simply reload the page in debug mode I can see that this request: http://192.168.11.33/global/system_medi ... nidlna.xml is returning:
Code: Select all
<root>
<NasType>
<lb type="str" dflt="" range="" rqurd=""/>
</NasType>
<Errors>
<Error>
<datetime>2023-02-28 10:38:12 (UTC)</datetime>
<errornum>256</errornum>
<errortype>User Notice</errortype>
<errormsg>Admin Server : Not valid request !</errormsg>
<scriptname>system_mediaserver-minidlna.xml</scriptname>
<scriptlinenum>9</scriptlinenum>
</Error>
</Errors>
</root>


I can see that I have a /share/1000/minidlna directory and the config looks OK.

In reading some of the other threads where users have reported errors with minidlna, I saw that one of the commands jocko asked for, so attempting to provide that info proactively. (Note that after running debugon and before running debugoff, I reloaded the minidlna web interface and clicked on "Install Server")

Code: Select all
root@lacie-ns2-fvdw:/share/1000/minidlna # debugon
root@lacie-ns2-fvdw:/share/1000/minidlna # debugoff
root@lacie-ns2-fvdw:/share/1000/minidlna # ps axf
  PID TTY      STAT   TIME COMMAND
    2 ?        S      0:00 [kthreadd]
    4 ?        I<     0:00  \_ [kworker/0:0H]
    6 ?        I<     0:00  \_ [mm_percpu_wq]
    7 ?        S      0:01  \_ [ksoftirqd/0]
    8 ?        I      0:04  \_ [rcu_preempt]
    9 ?        I      0:00  \_ [rcu_sched]
   10 ?        I      0:00  \_ [rcu_bh]
   11 ?        I<     0:00  \_ [netns]
   12 ?        I      0:00  \_ [kworker/u2:1]
  279 ?        S      0:00  \_ [oom_reaper]
  280 ?        I<     0:00  \_ [writeback]
  282 ?        I<     0:00  \_ [crypto]
  283 ?        I<     0:00  \_ [kintegrityd]
  285 ?        I<     0:00  \_ [kblockd]
  291 ?        I<     0:00  \_ [ata_sff]
  309 ?        I<     0:00  \_ [md]
  401 ?        I<     0:00  \_ [rpciod]
  402 ?        I<     0:00  \_ [xprtiod]
  403 ?        S      0:02  \_ [kswapd0]
  415 ?        I<     0:00  \_ [nfsiod]
  416 ?        I<     0:00  \_ [cifsiod]
  417 ?        I<     0:00  \_ [cifsoplockd]
  418 ?        S      0:00  \_ [jfsIO]
  422 ?        S      0:00  \_ [jfsCommit]
  423 ?        S      0:00  \_ [jfsSync]
  424 ?        I<     0:00  \_ [xfsalloc]
  425 ?        I<     0:00  \_ [xfs_mru_cache]
  568 ?        S      0:00  \_ [scsi_eh_0]
  569 ?        I<     0:00  \_ [scsi_tmf_0]
  572 ?        S      0:00  \_ [scsi_eh_1]
  573 ?        I<     0:00  \_ [scsi_tmf_1]
  576 ?        I      0:00  \_ [kworker/u2:2]
  577 ?        I<     0:00  \_ [smflush]
  578 ?        S      0:00  \_ [spi0]
  670 ?        S<     0:00  \_ [aoe_tx0]
  671 ?        S<     0:00  \_ [aoe_ktio0]
  694 ?        I<     0:00  \_ [raid5wq]
  697 ?        I<     0:00  \_ [dm_bufio_cache]
  698 ?        I<     0:00  \_ [kmpathd]
  699 ?        I<     0:00  \_ [kmpath_handlerd]
  716 ?        I<     0:00  \_ [ipv6_addrconf]
  719 ?        I<     0:00  \_ [dsa_ordered]
  730 ?        I<     0:00  \_ [kworker/0:1H]
  731 ?        S      0:00  \_ [jbd2/sda7-8]
  732 ?        I<     0:00  \_ [ext4-rsv-conver]
  749 ?        D      0:00  \_ [jbd2/sda1-8]
  750 ?        I<     0:00  \_ [ext4-rsv-conver]
  782 ?        I<     0:00  \_ [iscsi_eh]
  805 ?        S      0:00  \_ [jbd2/sda5-8]
  806 ?        I<     0:00  \_ [ext4-rsv-conver]
 1297 ?        S      0:00  \_ [jbd2/sda8-8]
 1298 ?        I<     0:00  \_ [ext4-rsv-conver]
 2296 ?        I      0:00  \_ [kworker/0:1]
 2363 ?        I      0:00  \_ [kworker/0:0]
 2364 ?        I      0:00  \_ [kworker/0:2]
    1 ?        Ss     0:03 init
  791 ?        Ss     0:00 /usr/sbin/buttonsd
  959 ?        S<s    0:00 /sbin/udevd --daemon
 1348 ?        Ss     0:05 /usr/bin/httpd -f httpd.conf -d /etc
 1349 ?        S      0:05  \_ /usr/bin/httpd -f httpd.conf -d /etc
 1358 ?        S      0:02  \_ /usr/bin/httpd -f httpd.conf -d /etc
 1352 ?        Ss     0:57 /usr/sbin/noflushd -n 15 /dev/sda
 1388 ?        Ss     0:00 /usr/bin/discoverd
 1396 ?        Ss     0:00 /usr/bin/rpcbind
 1414 ?        Ss     0:00 dropbear -p 22 -r /rw_fs/etc/dropbear/dropbear_rsa_ho
 2341 ?        Ss     0:00  \_ dropbear -p 22 -r /rw_fs/etc/dropbear/dropbear_rs
 2342 pts/0    Ss     0:00      \_ -sh
 2429 pts/0    R+     0:00          \_ ps axf
 1433 ?        Ss     0:00 /usr/sbin/hostd 7200
 1484 ?        Ss     0:03 /usr/sbin/nmbd -D -l /var/log/samba
 1486 ?        Ss     0:00 /usr/sbin/smbd -D -l /var/log/samba
 1491 ?        S      0:00  \_ /usr/sbin/smbd -D -l /var/log/samba
root@lacie-ns2-fvdw:/share/1000/minidlna # cat /var/log/messages
Feb 28 10:53:24 lacie-ns2-fvdw syslog.info syslogd started: BusyBox v1.21.0
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(36)[1349]: nasapi: lock time = 0
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(49)[1349]: calling 'mrvlGetVolumeAddons'
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(484)[1349]: mrvlGetVolumeAddons Return Code: 1000
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(36)[1349]: nasapi: lock time = 0
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(49)[1349]: calling 'mrvlMinidlnaServer installed'
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(484)[1349]: mrvlMinidlnaServer Return Code:
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(36)[1349]: nasapi: lock time = 0
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(49)[1349]: calling 'mrvlMinidlnaServer running'
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(484)[1349]: mrvlMinidlnaServer Return Code:
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(36)[1349]: nasapi: lock time = 0
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(49)[1349]: calling 'mrvlMinidlnaServer hasupdate'
Feb 28 10:53:34 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:34] nasapi.inc(484)[1349]: mrvlMinidlnaServer Return Code: 0
Feb 28 10:53:38 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:38] nasapi.inc(36)[1358]: nasapi: lock time = 0
Feb 28 10:53:38 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:38] nasapi.inc(49)[1358]: calling 'mrvlGetVolumeAddons'
Feb 28 10:53:38 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:38] nasapi.inc(484)[1358]: mrvlGetVolumeAddons Return Code: 1000
Feb 28 10:53:38 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:38] nasapi.inc(36)[1358]: nasapi: lock time = 0
Feb 28 10:53:38 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:38] nasapi.inc(49)[1358]: calling 'mrvlMinidlnaServer installed'
Feb 28 10:53:38 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:38] nasapi.inc(484)[1358]: mrvlMinidlnaServer Return Code:
Feb 28 10:53:38 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:38] nasapi.inc(36)[1358]: nasapi: lock time = 0
Feb 28 10:53:38 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:38] nasapi.inc(49)[1358]: calling 'mrvlMinidlnaServer install'
Feb 28 10:53:39 lacie-ns2-fvdw authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/bin/killall -9 minidlna
Feb 28 10:53:39 lacie-ns2-fvdw authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/bin/unlink /var/run/minidlna.pid
Feb 28 10:53:39 lacie-ns2-fvdw authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/bin/unlink /direct-usb/minidlna/mfvdw.conf
Feb 28 10:53:39 lacie-ns2-fvdw authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/usr/bin/unlink /direct-usb/minidlna/database/minidlna.log
Feb 28 10:53:39 lacie-ns2-fvdw authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/chmod 777 /share/1000/fvdw/addons/
Feb 28 10:53:39 lacie-ns2-fvdw authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/chmod 666 /rw_fs/etc/.loginplugout
Feb 28 10:53:39 lacie-ns2-fvdw authpriv.notice sudo:   nobody : TTY=unknown ; PWD=/usr/htdocs/global ; USER=root ; COMMAND=/bin/chmod 600 /rw_fs/etc/.loginplugout
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] sysfunc_addon_download.finc(30)[1358]: Failed to get credentials
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] sysfunc_minidlna_server.finc(71)[1358]: Fail: could not install mpd
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(484)[1358]: mrvlMinidlnaServer Return Code: 17
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(36)[1358]: nasapi: lock time = 0
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(49)[1358]: calling 'mrvlGetFTPStatus'
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(484)[1358]: mrvlGetFTPStatus Return Code: 0
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(36)[1358]: nasapi: lock time = 0
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(49)[1358]: calling 'mrvlMinidlnaServer installed'
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(484)[1358]: mrvlMinidlnaServer Return Code:
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(36)[1358]: nasapi: lock time = 0
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(49)[1358]: calling 'mrvlMinidlnaServer running'
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(484)[1358]: mrvlMinidlnaServer Return Code:
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(36)[1358]: nasapi: lock time = 0
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(49)[1358]: calling 'mrvlMinidlnaServer hasupdate'
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] nasapi.inc(484)[1358]: mrvlMinidlnaServer Return Code: 0
Feb 28 10:54:03 lacie-ns2-fvdw syslog.info syslogd exiting


In the other thread viewtopic.php?f=11&t=3669. Jocko then asked the other user to run
Code: Select all
ldd /usr/local/bin/minidlna       (check if there is no dependency issue)
ls -al /direct-usb/minidlna/database/files.db        (datafile exists ?)


I noticed that I do not seem to have ANY /usr/local directory!
Code: Select all
root@lacie-ns2-fvdw:/share/1000/minidlna # ls -l /usr/local
lrwxrwxrwx  1 root root 23 2023-02-26 18:41 /usr/local -> /share/1000/fvdw/addons
root@lacie-ns2-fvdw:/share/1000/minidlna # ls -l /share/1000/fvdw/addons/
total 0


Is it possible that updating the patches somehow killed the addons directory? Is there something I can remove that will allow a fresh installation?
jpjpjp
Donator VIP
Donator VIP
 
Posts: 23
Joined: Wed Jan 28, 2015 12:48 am

Re: Another minidlna issue after upgrading from 17.x to 18.2

Postby Jocko » Mon May 01, 2023 8:07 am

Hi jpjpjp,

Sorry I did not notice your post.

So the issue is here
Code: Select all
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] sysfunc_addon_download.finc(30)[1358]: Failed to get credentials
That means :
- either you did not yet enter your plugout credentials (jpjpjp account) like detailled here (viewtopic.php?f=7&t=3224)
- or you changed your password and you did not update it on your nas

note:
jpjpjp wrote:When I simply reload the page in debug mode I can see that this request: http://192.168.11.33/global/system_medi ... nidlna.xml is returning:
Code: Select all
<root>
<NasType>
<lb type="str" dflt="" range="" rqurd=""/>
</NasType>
<Errors>
<Error>
<datetime>2023-02-28 10:38:12 (UTC)</datetime>
<errornum>256</errornum>
<errortype>User Notice</errortype>
<errormsg>Admin Server : Not valid request !</errormsg>
<scriptname>system_mediaserver-minidlna.xml</scriptname>
<scriptlinenum>9</scriptlinenum>
</Error>
</Errors>
</root>
This is the expected behaviour. Your are not allowed to run firmware requests out of its environment except for few ones like to standby the nas
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Another minidlna issue after upgrading from 17.x to 18.2

Postby Jocko » Mon May 01, 2023 8:08 am

Hi jpjpjp,

Sorry I did not notice your post.

So the issue is here
Code: Select all
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] sysfunc_addon_download.finc(30)[1358]: Failed to get credentials
That means :
- either you did not yet enter your plugout credentials (jpjpjp account) like detailled here (viewtopic.php?f=7&t=3224)
- or you changed your password and you did not update it on your nas

note:
jpjpjp wrote:When I simply reload the page in debug mode I can see that this request: http://192.168.11.33/global/system_medi ... nidlna.xml is returning:
Code: Select all
<root>
<NasType>
<lb type="str" dflt="" range="" rqurd=""/>
</NasType>
<Errors>
<Error>
<datetime>2023-02-28 10:38:12 (UTC)</datetime>
<errornum>256</errornum>
<errortype>User Notice</errortype>
<errormsg>Admin Server : Not valid request !</errormsg>
<scriptname>system_mediaserver-minidlna.xml</scriptname>
<scriptlinenum>9</scriptlinenum>
</Error>
</Errors>
</root>
This is the expected behaviour. Your are not allowed to run firmware requests out of its environment except for few ones like to standby the nas
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Another minidlna issue after upgrading from 17.x to 18.2

Postby Jocko » Mon May 01, 2023 8:09 am

Hi jpjpjp,

Sorry I did not notice your post.

So the issue is here
Code: Select all
Feb 28 10:53:39 lacie-ns2-fvdw local0.warn API[2023/02/28 10:53:39] sysfunc_addon_download.finc(30)[1358]: Failed to get credentials
That means :
- either you did not yet enter your plugout credentials (jpjpjp account) like detailed here (viewtopic.php?f=7&t=3224)
- or you changed your password and you did not update it on your nas

note:
When I simply reload the page in debug mode I can see that this request: http://192.168.11.33/global/system_medi ... nidlna.xml is returning:
Code: Select all
<root>
<NasType>
<lb type="str" dflt="" range="" rqurd=""/>
</NasType>
<Errors>
<Error>
<datetime>2023-02-28 10:38:12 (UTC)</datetime>
<errornum>256</errornum>
<errortype>User Notice</errortype>
<errormsg>Admin Server : Not valid request !</errormsg>
<scriptname>system_mediaserver-minidlna.xml</scriptname>
<scriptlinenum>9</scriptlinenum>
</Error>
</Errors>
</root>
This is the expected behaviour. Your are not allowed to run firmware requests out of its environment except for few ones like to standby the nas
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France


Return to Lacie Network Space vs2 and max version

Who is online

Users browsing this forum: No registered users and 4 guests