plugout.net

Hi,

I've just installed ver 18.2 and recoved old cloudbox back to work. great!

first thing was enabling miniDLNM and i noticed something i would like to share here - is this some issue or my wrong operation.

i added 'public' folder to miniDLNA.
when uploading media file to public folder via FTP they are nicely detected on my TV. but when i uploaded a file via Samba they do exist on public folder but they are not detected to be displayed on TV.
unfortunately samba is my preferred way of uploading files to dlna server.

when looking at owner and access rights the files do not differ - below 3 first are uploded via FTP while 3 lower via SMB.
any advice appreciated.

root@fvdwsl-base:/share/1000/public # ls -la
total 146016
drwxrwxrwx 2 root root 4096 2028-04-21 22:55 .
drwxrwxr-x 7 root sys 4096 2028-04-21 23:35 ..
-rw-rw-rw- 1 public public 2395156 2028-04-21 22:54 IMG20220325211724.jpg
-rw-rw-rw- 1 public public 2866136 2028-04-21 22:54 IMG20220325211729.jpg
-rw-rw-rw- 1 public public 2001106 2028-04-21 22:54 IMG20220325211744.jpg
-rw-rw-rw- 1 public public 4917388 2022-03-28 22:46 IMG_20220326_080904.jpg
-rw-rw-rw- 1 public public 4489698 2022-03-28 22:46 IMG_20220326_080953.jpg
-rw-rw-rw- 1 public public 4803972 2022-03-28 22:46 IMG_20220326_091145.jpg

regards

the only difference is timestamp
when doing this command below the files get detected on TV
touch -d 2028-04-21 /share/1000/public/*

my cloudbox takes future date 2028-04-21 as system time (no NTP server configured), and apparently files uploded via FTP are marked with the cloudbox system time.
files uploaded via samba were marked with their original creation date, but this date is apparently 'too old' for miniDLNA to serve the file as media ???

Hi

For investigating I need this additional information, can you post these outputs

Code: Select all

date -u
hwclock -r

and how to do set datetime at 2028 on your cloudbox ?

hi,

outputs requested:
root@fvdwsl-base:/ # date -u
Mon Apr 24 02:51:24 UTC 2028
root@fvdwsl-base:/ # hwclock -r
Mon Apr 24 02:51:47 2028 0.000000 seconds

the date 2028 sets automatically after reboot. I set in web GUI manually but it reverted to 2028 after reboot.
i should have configure NTP anyway, but this DLNA issue was my main concern, fortunately i found workaround with 'touch' so not big problem any longer.

regards

Hi,

lkopyt wrote:the date 2028 sets automatically after reboot. I set in web GUI manually but it reverted to 2028 after reboot.

This is amazing.
If I remember well there is no battery to save the hardware clock on a cloudbox. So you lose your time settings it is the expected behaviour when you reboot the nas but the fw should not set as default datetime 2028... Then the fw uses 2018/01/01 as default datetime :scratch :scratch :scratch
Can you post the outputs

Code: Select all

ls -l /etc/init.d/rcS
grep 2018 -A 4 /etc/init.d/rcS
grep 'device =' -A 4 /boot.log

lkopyt wrote:I should have configure NTP anyway, but this DLNA issue was my main concern

Nope I think the issues are linked.
On cloudbox you have to use a ntp server to keep the right time and it is easy to set it. Here you can find a ntp server listhttps://gist.github.com/mutin-sa/eea1c396b1e610a2da1e5550d94b0453

Then after selecting the ntp servers, repeat your test to check if minidlna detects the new files after copying from samba server

hi,

I've just collected the outputs.

Code: Select all

root@fvdwsl-base:/ # ls -l /etc/init.d/rcS
-rwxr-xr-x  1 root root 37656 2020-09-20 18:08 /etc/init.d/rcS
root@fvdwsl-base:/ # grep 2018 -A 4 /etc/init.d/rcS
 if [ $year -lt 2018 ]
 then
  echo "initializing date" >> boot.log
  /bin/date -s 2018.01.01-12:00
  /bin/date >> boot.log
 else
  /bin/date >> boot.log
 fi
root@fvdwsl-base:/ # date
Wed Apr 26 01:13:14 CEST 2028
root@fvdwsl-base:/ # grep 'device =' -A 4 /boot.log
device = cloudbox
source = buttons-cloudbox
buttons-nwsp2 daemon started
Keep old Min free memory=2000
Tue Apr 25 00:21:15 CEST 2028

configured NTP and wiull see whether it changes.

regards