NAS access

[Star6key]

...
Is your T4's DLNA server configured to point at the share? Perhaps it is trying to index the files on the share?

Hammer, meet nail.

8192_0_1_0_0_0_0_0_0_0_20180927135710.jpg (104.41 KiB) Viewed 3431 times

Thanks again MrQuade.

[Star6key]

Didn't see the point in starting a new topic, so I'm piggybacking on this one.

I have symbolic links setup for a few of my video directories on the PC. It all works fine. However, from time to time, I disable the share in the Mount Manager (don't ask). For the life of me, I don't know how to get the SymLink to reappear in the Media window, once I reactivate the share. In frustration, I just reboot the unit which brings it back.

Can anyone help this poor sod?

[Grumpy_Geoff]

I don't know how to get the SymLink to reappear in the Media window, once I reactivate the share. In frustration, I just reboot the unit which brings it back.

Are you using FSTAB (mount at boot)?
I'm using AUTOFS (mount as needed) and that's not my experience, as once the mount has been re-activated then the symlink re-appears in the media selection list.

[Star6key]

I don't know how to get the SymLink to reappear in the Media window, once I reactivate the share. In frustration, I just reboot the unit which brings it back.

Are you using FSTAB (mount at boot)?
I'm using AUTOFS (mount as needed) and that's not my experience, as once the mount has been re-activated then the symlink re-appears in the media selection list.

8192_0_1_0_0_0_0_0_0_0_20190404140944.jpg (162.01 KiB) Viewed 3661 times

[Grumpy_Geoff]

When reactivating the mount, when the last popup ("activated") appears are you either letting it timeout (9 secs) or pressing OK on it, rather than EXIT?
(first popup is "update existing mount question", second popup is "mounts being updated" and this one restarts the network).

When it doesn't reappear, is the entry for MyTVShows in /etc/enigma2/automounts.xml set to <active>True</active>?

Is the corresponding entry for it missing from file /etc/auto.network (the entry should be:
MyTVShows -{a bunch of options} ://192.168.1.120/NonAnime)?

[Star6key]

When reactivating the mount, when the last popup ("activated") appears are you either letting it timeout (9 secs) or pressing OK on it, rather than EXIT?
(first popup is "update existing mount question", second popup is "mounts being updated" and this one restarts the network).
...

Tried all 3 (timeout, OK, Exit). Makes no difference.

...
When it doesn't reappear, is the entry for MyTVShows in /etc/enigma2/automounts.xml set to <active>True</active>?
...

<autofs>
<cifs>
<mount>
<active>True</active>
<hdd_replacement>False</hdd_replacement>
<ip>192.168.1.120</ip>
<sharename>MyTVShows</sharename>
<sharedir>NonAnime</sharedir>
<options>rw,utf8,vers=2.1</options>
<username>Me</username>
<password>(deleted by me)</password>
</mount>
</cifs>
</autofs>

...
Is the corresponding entry for it missing from file /etc/auto.network (the entry should be:
MyTVShows -{a bunch of options} ://192.168.1.120/NonAnime)?

# automounter configuration
MyTVShows -fstype=cifs,user=Me,pass=(deleted by me),rw,iocharset=utf8,vers=2.1,cache=loose ://192.168.1.120/NonAnime

[Grumpy_Geoff]

Got me beat!

I stopped using symbolic links quite a while ago as they slowed down the media selection list if the target share was offline. There's another problem I can't quite recall - something to do with deleting and trashes and the deleted file being copied to local.

Instead of rebooting, can you get to the share via YELLOW/Locations in the media selection list?

[Star6key]

Got me beat!

I stopped using symbolic links quite a while ago as they slowed down the media selection list if the target share was offline. There's another problem I can't quite recall - something to do with deleting and trashes and the deleted file being copied to local.

Instead of rebooting, can you get to the share via YELLOW/Locations in the media selection list?

Going to Locations, I see /media/autofs (where the directories would be), but when I select it, it's empty.
When I reboot and go to /media/autofs, the directories are back.

I even deleted the mount, created a new one (with a different name, and no SymLink), but I see the same behaviour in the the Autofs directory.

Buggered if I know what's going on.

[MrQuade]

I stopped using symbolic links quite a while ago as they slowed down the media selection list if the target share was offline. There's another problem I can't quite recall - something to do with deleting and trashes and the deleted file being copied to local.

Maybe I'm not following you exactly, but it sounds like this isn't a problem with the symlinks. If the autofs directory is empty, it means that the mounts haven't been re-mounted, so the symlink has nowhere to point to.

[Grumpy_Geoff]

Going to Locations, I see /media/autofs (where the directories would be), but when I select it, it's empty.
When I reboot and go to /media/autofs, the directories are back.

All of the mounts have disappeared? That sounds like the command /etc/init.d/autofs stop succeeds but the /etc/init.d/autofs start does not.

Perhaps enable debug logging.

[Star6key]

I stopped using symbolic links quite a while ago as they slowed down the media selection list if the target share was offline. There's another problem I can't quite recall - something to do with deleting and trashes and the deleted file being copied to local.

Maybe I'm not following you exactly, but it sounds like this isn't a problem with the symlinks. If the autofs directory is empty, it means that the mounts haven't been re-mounted, so the symlink has nowhere to point to.

You seem to be having a lot of trouble with Trevor lately... you've quoted the wrong person.

[Star6key]

Going to Locations, I see /media/autofs (where the directories would be), but when I select it, it's empty.
When I reboot and go to /media/autofs, the directories are back.

All of the mounts have disappeared? That sounds like the command /etc/init.d/autofs stop succeeds but the /etc/init.d/autofs start does not.

Perhaps enable debug logging.

Tomorrow.

[MrQuade]

You seem to be having a lot of trouble with Trevor lately... you've quoted the wrong person.

Ha! I quoted the right person with the wrong person's text.

That comment was directed at your last post where you said

Going to Locations, I see /media/autofs (where the directories would be), but when I select it, it's empty.

Apologies

[Grumpy_Geoff]

Going to Locations, I see /media/autofs (where the directories would be), but when I select it, it's empty.
When I reboot and go to /media/autofs, the directories are back.

All of the mounts have disappeared? That sounds like the command /etc/init.d/autofs stop succeeds but the /etc/init.d/autofs start does not.

Perhaps enable debug logging.

Tomorrow.

Try a manual network restart as well and see if that makes a difference (MENU>>Setup>>Network>>Network restart).

[Star6key]

Code: Select all

{630}<  2664.047> KEY: 139 make KEY_MENU ('MENU',)
{630}<  2664.048> [ActionMap] InfobarMenuActions mainMenu
{630}<  2664.059> Skip plugin => AutoTimer
{630}<  2664.061> Skip plugin => Front Panel Update
{630}<  2664.063> Skip plugin => OpenWebif
{630}<  2664.065> Skip plugin => Picture player
{630}<  2664.066> Skip plugin => Software management
{630}<  2664.067> Skip plugin => YouTube TV Settings
{630}<  2664.072> Skip menu => Media player
{630}<  2664.087> [Skin] processing screen GeneralMenu:
{630}<  2664.198> [Skin] processing screen GeneralMenuSummary:
{630}<  2664.201> [SCREENNAME]  GeneralMenuSummary
{630}<  2664.222> [SCREENNAME]  GeneralMenu
{630}<  2664.242> KEY: 139 break KEY_MENU ('MENU',)
{630}<  2665.376> KEY: 106 make KEY_RIGHT ('RIGHT',)
{630}<  2665.377> [ActionMap] DirectionActions right
{630}<  2665.567> KEY: 106 break KEY_RIGHT ('RIGHT',)
{630}<  2665.763> KEY: 106 make KEY_RIGHT ('RIGHT',)
{630}<  2665.763> [ActionMap] DirectionActions right
{630}<  2665.956> KEY: 106 break KEY_RIGHT ('RIGHT',)
{630}<  2667.459> KEY: 352 make KEY_OK ('OK',)
{630}<  2667.460> [ActionMap] OkCancelActions ok
{630}<  2667.584> [Skin] processing screen GeneralSetup:
{630}<  2667.678> [Skin] processing screen SimpleSummary:
{630}<  2667.758> [SCREENNAME]  ['GeneralSetup_summary', 'SimpleSummary']
{630}<  2667.765> [SCREENNAME]  GeneralSetup
{630}<  2667.770> KEY: 352 break KEY_OK ('OK',)
{630}<  2670.801> KEY: 103 make KEY_UP ('UP',)
{630}<  2670.801> [ActionMap] WizardActions up
{630}<  2670.992> KEY: 103 break KEY_UP ('UP',)
{630}<  2671.186> KEY: 103 make KEY_UP ('UP',)
{630}<  2671.187> [ActionMap] WizardActions up
{630}<  2671.378> KEY: 103 break KEY_UP ('UP',)
{630}<  2671.601> KEY: 103 make KEY_UP ('UP',)
{630}<  2671.602> [ActionMap] WizardActions up
{630}<  2671.792> KEY: 103 break KEY_UP ('UP',)
{630}<  2672.389> KEY: 103 make KEY_UP ('UP',)
{630}<  2672.389> [ActionMap] WizardActions up
{630}<  2672.580> KEY: 103 break KEY_UP ('UP',)
{630}<  2673.407> KEY: 106 make KEY_RIGHT ('RIGHT',)
{630}<  2673.408> [ActionMap] SetupActions right
{630}<  2673.598> KEY: 106 break KEY_RIGHT ('RIGHT',)
{630}<  2673.963> KEY: 108 make KEY_DOWN ('DOWN',)
{630}<  2673.963> [ActionMap] WizardActions down
{630}<  2674.154> KEY: 108 break KEY_DOWN ('DOWN',)
{630}<  2674.868> KEY: 352 make KEY_OK ('OK',)
{630}<  2674.868> [ActionMap] SetupActions ok
{630}<  2674.921> [Skin] processing screen AutoMountManager:
{630}<  2674.994> [Skin] processing screen PluginBrowserSummary:
{630}<  2675.024> [SCREENNAME]  PluginBrowserSummary
{630}<  2675.033> [SCREENNAME]  AutoMountManager
{630}<  2675.060> KEY: 352 break KEY_OK ('OK',)
{630}<  2675.976> KEY: 108 make KEY_DOWN ('DOWN',)
{630}<  2676.167> KEY: 108 break KEY_DOWN ('DOWN',)
{630}<  2676.624> KEY: 352 make KEY_OK ('OK',)
{630}<  2676.624> [ActionMap] WizardActions ok
{630}<  2676.678> [Skin] processing screen AutoMountView:
{630}<  2676.767> [Skin] processing screen PluginBrowserSummary:
{630}<  2676.796> [SCREENNAME]  PluginBrowserSummary
{630}<  2676.803> [SCREENNAME]  AutoMountView
{630}<  2676.816> KEY: 352 break KEY_OK ('OK',)
{630}<  2679.776> KEY: 352 make KEY_OK ('OK',)
{630}<  2679.776> [ActionMap] WizardActions ok
{630}<  2679.841> [Skin] processing screen AutoMountEdit:
{630}<  2679.949> [Skin] processing screen SetupSummary:
{630}<  2679.979> [SCREENNAME]  SetupSummary
{630}<  2679.986> [SCREENNAME]  AutoMountEdit
{630}<  2679.991> KEY: 352 break KEY_OK ('OK',)
{630}<  2681.623> KEY: 108 make KEY_DOWN ('DOWN',)
{630}<  2681.814> KEY: 108 break KEY_DOWN ('DOWN',)
{630}<  2682.190> KEY: 105 make KEY_LEFT ('LEFT',)
{630}<  2682.191> [ActionMap] SetupActions left
{630}<  2682.191> [ActionMap] unknown action SetupActions/left! typo in keymap?
{630}<  2682.192> [ActionMap] SetupActions left
{630}<  2682.382> KEY: 105 break KEY_LEFT ('LEFT',)
{630}<  2683.665> KEY: 399 make KEY_GREEN ('GREEN',)
{630}<  2683.665> [ActionMap] SetupActions save
{630}<  2683.666> [ActionMap] unknown action SetupActions/save! typo in keymap?
{630}<  2683.666> [ActionMap] SetupActions save
{630}<  2683.666> [ActionMap] unknown action SetupActions/save! typo in keymap?
{630}<  2683.856> KEY: 399 break KEY_GREEN ('GREEN',)
{630}<  2683.857> [ActionMap] ColorActions green
{630}<  2683.867> [Skin] processing screen MessageBox:
{630}<  2683.934> [Skin] processing screen MessageBox_summary:
{630}<  2683.939> [SCREENNAME]  ['MessageBox_summary', 'SimpleSummary']
{630}<  2683.941> [SCREENNAME]  ['MessageBox']
{630}<  2685.527> KEY: 108 make KEY_DOWN ('DOWN',)
{630}<  2685.527> [ActionMap] DirectionActions down
{630}<  2685.719> KEY: 108 break KEY_DOWN ('DOWN',)
{630}<  2686.105> KEY: 352 make KEY_OK ('OK',)
{630}<  2686.105> [ActionMap] MsgBoxActions ok
{630}<  2686.108> [SCREENNAME]  SetupSummary
{630}<  2686.117> [SCREENNAME]  AutoMountEdit
{630}<  2686.128> [Skin] processing screen MessageBox:
{630}<  2686.155> [Skin] processing screen MessageBox_summary:
{630}<  2686.160> [SCREENNAME]  ['MessageBox_summary', 'SimpleSummary']
{630}<  2686.161> [SCREENNAME]  ['MessageBox']
{630}<  2686.171> command ['/etc/init.d/autofs stop', 'sleep 2']
{630}<  2686.171> [Console] command: /etc/init.d/autofs stop
{630}<  2686.172> [eConsoleAppContainer] Starting /bin/sh
{630}<  2686.296> KEY: 352 break KEY_OK ('OK',)
{630}<  2687.315> [Console] finished: /etc/init.d/autofs stop
{630}<  2687.315> [eBatch] retval=0, cmds left=1, data:
Stopping automount: done.
{630}<  2687.316> 
{630}<  2687.316> [Console] command: sleep 2
{630}<  2687.316> [eConsoleAppContainer] Starting /bin/sh
{630}<  2689.333> [Console] finished: sleep 2
{630}<  2689.333> [eBatch] retval=0, cmds left=0, data:
{630}<  2689.333> 
{630}<  2689.334> command ['/etc/init.d/autofs stop', 'sleep 2']
{630}<  2689.335> [Console] command: /etc/init.d/autofs stop
{630}<  2689.335> [eConsoleAppContainer] Starting /bin/sh
{630}<  2689.410> [Console] finished: /etc/init.d/autofs stop
{630}<  2689.410> [eBatch] retval=0, cmds left=1, data:
Stopping automount: done.
{630}<  2689.410> 
{630}<  2689.411> [Console] command: sleep 2
{630}<  2689.411> [eConsoleAppContainer] Starting /bin/sh
{630}<  2691.427> [Console] finished: sleep 2
{630}<  2691.428> [eBatch] retval=0, cmds left=0, data:
{630}<  2691.428> 
{630}<  2692.431> [SCREENNAME]  SetupSummary
{630}<  2692.440> [SCREENNAME]  AutoMountEdit
{630}<  2692.450> [Skin] processing screen MessageBox:
{630}<  2692.477> [Skin] processing screen MessageBox_summary:
{630}<  2692.482> [SCREENNAME]  ['MessageBox_summary', 'SimpleSummary']
{630}<  2692.484> [SCREENNAME]  ['MessageBox']
{630}<  2694.278> KEY: 352 make KEY_OK ('OK',)
{630}<  2694.278> [ActionMap] MsgBoxActions ok
{630}<  2694.281> [SCREENNAME]  SetupSummary
{630}<  2694.290> [SCREENNAME]  AutoMountEdit
{630}<  2694.297> [SCREENNAME]  PluginBrowserSummary
{630}<  2694.313> [SCREENNAME]  AutoMountView
{630}<  2694.469> KEY: 352 break KEY_OK ('OK',)
{630}<  2756.664> KEY: 108 make KEY_DOWN ('DOWN',)
{630}<  2756.855> KEY: 108 break KEY_DOWN ('DOWN',)
{630}<  2760.650> KEY: 352 make KEY_OK ('OK',)
{630}<  2760.651> [ActionMap] WizardActions ok
{630}<  2760.716> [Skin] processing screen AutoMountEdit:
{630}<  2760.812> [Skin] processing screen SetupSummary:
{630}<  2760.841> [SCREENNAME]  SetupSummary
{630}<  2760.848> [SCREENNAME]  AutoMountEdit
{630}<  2760.853> KEY: 352 break KEY_OK ('OK',)
{630}<  2762.008> KEY: 108 make KEY_DOWN ('DOWN',)
{630}<  2762.200> KEY: 108 break KEY_DOWN ('DOWN',)
{630}<  2762.674> KEY: 106 make KEY_RIGHT ('RIGHT',)
{630}<  2762.675> [ActionMap] SetupActions right
{630}<  2762.675> [ActionMap] unknown action SetupActions/right! typo in keymap?
{630}<  2762.676> [ActionMap] SetupActions right
{630}<  2762.865> KEY: 106 break KEY_RIGHT ('RIGHT',)
{630}<  2764.530> KEY: 399 make KEY_GREEN ('GREEN',)
{630}<  2764.531> [ActionMap] SetupActions save
{630}<  2764.531> [ActionMap] unknown action SetupActions/save! typo in keymap?
{630}<  2764.531> [ActionMap] SetupActions save
{630}<  2764.532> [ActionMap] unknown action SetupActions/save! typo in keymap?
{630}<  2764.723> KEY: 399 break KEY_GREEN ('GREEN',)
{630}<  2764.723> [ActionMap] ColorActions green
{630}<  2764.733> [Skin] processing screen MessageBox:
{630}<  2764.759> [Skin] processing screen MessageBox_summary:
{630}<  2764.764> [SCREENNAME]  ['MessageBox_summary', 'SimpleSummary']
{630}<  2764.765> [SCREENNAME]  ['MessageBox']
{630}<  2766.192> KEY: 108 make KEY_DOWN ('DOWN',)
{630}<  2766.192> [ActionMap] DirectionActions down
{630}<  2766.383> KEY: 108 break KEY_DOWN ('DOWN',)
{630}<  2767.181> KEY: 352 make KEY_OK ('OK',)
{630}<  2767.181> [ActionMap] MsgBoxActions ok
{630}<  2767.184> [SCREENNAME]  SetupSummary
{630}<  2767.193> [SCREENNAME]  AutoMountEdit
{630}<  2767.203> [Skin] processing screen MessageBox:
{630}<  2767.229> [Skin] processing screen MessageBox_summary:
{630}<  2767.430> [SCREENNAME]  ['MessageBox_summary', 'SimpleSummary']
{630}<  2767.431> [SCREENNAME]  ['MessageBox']
{630}<  2767.441> command ['/etc/init.d/autofs stop', 'sleep 2', '/etc/init.d/autofs start']
{630}<  2767.441> [Console] command: /etc/init.d/autofs stop
{630}<  2767.442> [eConsoleAppContainer] Starting /bin/sh
{630}<  2767.453> KEY: 352 break KEY_OK ('OK',)
{630}<  2767.531> [Console] finished: /etc/init.d/autofs stop
{630}<  2767.531> [eBatch] retval=0, cmds left=2, data:
Stopping automount: done.
{630}<  2767.532> 
{630}<  2767.532> [Console] command: sleep 2
{630}<  2767.532> [eConsoleAppContainer] Starting /bin/sh
{630}<  2769.549> [Console] finished: sleep 2
{630}<  2769.550> [eBatch] retval=0, cmds left=1, data:
{630}<  2769.550> 
{630}<  2769.551> [Console] command: /etc/init.d/autofs start
{630}<  2769.551> [eConsoleAppContainer] Starting /bin/sh
{630}<  2770.662> [Console] finished: /etc/init.d/autofs start
{630}<  2770.662> [eBatch] retval=0, cmds left=0, data:
Starting automount: done.
{630}<  2770.662> 
{630}<  2770.667> command ['/etc/init.d/autofs stop', 'sleep 2']
{630}<  2770.668> [Console] command: /etc/init.d/autofs stop
{630}<  2770.668> [eConsoleAppContainer] Starting /bin/sh
{630}<  2771.799> [Console] finished: /etc/init.d/autofs stop
{630}<  2771.799> [eBatch] retval=0, cmds left=1, data:
Stopping automount: done.
{630}<  2771.799> 
{630}<  2771.799> [Console] command: sleep 2
{630}<  2771.800> [eConsoleAppContainer] Starting /bin/sh
{630}<  2773.817> [Console] finished: sleep 2
{630}<  2773.817> [eBatch] retval=0, cmds left=0, data:
{630}<  2773.817> 
{630}<  2774.821> [SCREENNAME]  SetupSummary
{630}<  2774.830> [SCREENNAME]  AutoMountEdit
{630}<  2774.841> [Skin] processing screen MessageBox:
{630}<  2774.867> [Skin] processing screen MessageBox_summary:
{630}<  2774.872> [SCREENNAME]  ['MessageBox_summary', 'SimpleSummary']
{630}<  2774.874> [SCREENNAME]  ['MessageBox']
{630}<  2776.094> KEY: 352 make KEY_OK ('OK',)
{630}<  2776.095> [ActionMap] MsgBoxActions ok
{630}<  2776.098> [SCREENNAME]  SetupSummary
{630}<  2776.107> [SCREENNAME]  AutoMountEdit
{630}<  2776.114> [SCREENNAME]  PluginBrowserSummary
{630}<  2776.132> [SCREENNAME]  AutoMountView
{630}<  2776.286> KEY: 352 break KEY_OK ('OK',)

Hmmm...

So it seems that with the mount running, I go in and stop it, which it does. I then start it, which it does, then right after that it stops it. That doesn't sound good.

[Star6key]

Ha! I quoted the right person with the wrong person's text.

That comment was directed at your last post where you said

Going to Locations, I see /media/autofs (where the directories would be), but when I select it, it's empty.

Apologies

No problem. It's not an issue with the SymLinks. I only created a new mount to rule it out.

[prl]

So it seems that with the mount running, I go in and stop it, which it does. I then start it, which it does, then right after that it stops it. That doesn't sound good.

While it may be possible to work it out by tracing the button presses and screen invocations in the log, it would make replication simpler if you said exactly what you mean by "start it" and "stop it". Which "it", and how started and stopped?

[Grumpy_Geoff]

...So it seems that with the mount running, I go in and stop it, which it does. I then start it, which it does, then right after that it stops it. That doesn't sound good.

I have 5 mounts listed in /etc/auto.network
When I reactivate a mount, I get 5 x command ['/etc/init.d/autofs stop', 'sleep 2', '/etc/init.d/autofs start'] listed in the debug log.

You have one listed -
{630}< 2767.441> command ['/etc/init.d/autofs stop', 'sleep 2', '/etc/init.d/autofs start']
... and then a half-baked one -
{630}< 2770.667> command ['/etc/init.d/autofs stop', 'sleep 2']

What happens on a manual network restart - any difference?

Are you still on 20190206 and haven't updated, perhaps there was a change?

[Star6key]

So it seems that with the mount running, I go in and stop it, which it does. I then start it, which it does, then right after that it stops it. That doesn't sound good.

While it may be possible to work it out by tracing the button presses and screen invocations in the log, it would make replication simpler if you said exactly what you mean by "start it" and "stop it". Which "it", and how started and stopped?

Reboot.
Open media list.
Press long blue (locations setting).
Select 'NonAnime' (the share name).
Get a display of all the folders. All good.

Goto main menu/setup/network/mount manager/mountpoints management.
(NonAnime has a green tick - active)
Select Nonanime.
Turn 'Active' off.
Press Save.
'A mount entry with this name... blah blah blah' - select 'Yes'.
'Please wait while ... blah blah'.
'Your network mount has been updated' (let it timeout).
(NonAnime has a yellow exclamation mark - inactive)
Exit back to live tv (hdmi in).

Goto main menu/setup/network/mount manager/mountpoints management.
(NonAnime has a yellow exclamation mark - inactive)
Select Nonanime.
Turn 'Active' on.
Press Save.
'A mount entry with this name... blah blah blah' - select 'Yes'.
'Please wait while ... blah blah'
'Your network mount has been updated' (let it timeout).
(NonAnime has a green tick - active)

Exit back to live tv (hdmi in).
Open media list.
Press long blue (locations setting).
Select 'NonAnime' (the share name).

'Directory '/media/autofs/nonanime/' does not exist'.

[Star6key]

...So it seems that with the mount running, I go in and stop it, which it does. I then start it, which it does, then right after that it stops it. That doesn't sound good.

I have 5 mounts listed in /etc/auto.network
When I reactivate a mount, I get 5 x command ['/etc/init.d/autofs stop', 'sleep 2', '/etc/init.d/autofs start'] listed in the debug log.

You have one listed -
{630}< 2767.441> command ['/etc/init.d/autofs stop', 'sleep 2', '/etc/init.d/autofs start']
... and then a half-baked one -
{630}< 2770.667> command ['/etc/init.d/autofs stop', 'sleep 2']

What happens on a manual network restart - any difference?

Are you still on 20190206 and haven't updated, perhaps there was a change?

System OE: OE-Alliance 4.1
Firmware version: beyonwiz 17.5.20190206 (17.5-819-gdd3f1fa)
Kernel / Drivers: 3.14.2 / 20180416

Manually restarted the network.

Exit back to live tv (hdmi in).
Open media list.
Press long blue (locations setting).
Select 'NonAnime' (the share name).

'Directory '/media/autofs/nonanime/' does not exist'.

[Grumpy_Geoff]

System OE: OE-Alliance 4.1
Firmware version: beyonwiz 17.5.20190206 (17.5-819-gdd3f1fa)
Kernel / Drivers: 3.14.2 / 20180416

Manually restarted the network.

Exit back to live tv (hdmi in).
Open media list.
Press long blue (locations setting).
Select 'NonAnime' (the share name).

'Directory '/media/autofs/nonanime/' does not exist'.

You have two mounts right?
Do you still have an inactive mount? That would match -

Code: Select all

<  2770.667> command ['/etc/init.d/autofs stop', 'sleep 2']

Can you attach a screenshot of Mountpoints management / Mount Viewer please.

Can you online update to 20190207 and try again?

[Star6key]

You have two mounts right?
Do you still have an inactive mount? That would match -

Code: Select all

<  2770.667> command ['/etc/init.d/autofs stop', 'sleep 2']

...

Yes and yes.

...
Can you attach a screenshot of Mountpoints management / Mount Viewer please.

Can you online update to 20190207 and try again?

System OE: OE-Alliance 4.1
Firmware version: beyonwiz 17.5.20190207 (17.5-819-gdd3f1fa)
Kernel / Drivers: 3.14.2 / 20180416

Updated, but get the same results.

8192_0_1_0_0_0_0_0_0_0_20190405133534.jpg (138.16 KiB) Viewed 3560 times

[prl]

I have 5 mounts listed in /etc/auto.network
When I reactivate a mount, I get 5 x command ['/etc/init.d/autofs stop', 'sleep 2', '/etc/init.d/autofs start'] listed in the debug log.

That seems excessive.

[prl]

So it seems that with the mount running, I go in and stop it, which it does. I then start it, which it does, then right after that it stops it. That doesn't sound good.

While it may be possible to work it out by tracing the button presses and screen invocations in the log, it would make replication simpler if you said exactly what you mean by "start it" and "stop it". Which "it", and how started and stopped?

Reboot.
Open media list.
Press long blue (locations setting).
...

Thanks. I'll try to replicate it.

[Grumpy_Geoff]

...
Can you attach a screenshot of Mountpoints management / Mount Viewer please.

Can you online update to 20190207 and try again?

System OE: OE-Alliance 4.1
Firmware version: beyonwiz 17.5.20190207 (17.5-819-gdd3f1fa)
Kernel / Drivers: 3.14.2 / 20180416

Updated, but get the same results.

8192_0_1_0_0_0_0_0_0_0_20190405133534.jpg

Previously you stated it as -
MyTVShows on //192.168.1.120/NonAnime

The screenshot doesn't have MyTVShows.
Have you renamed local share 'MyTVShows' as 'NonAnime' (or vice versa)?

I'm not sure having a space in a server share name ('My Movies') is good practice.

[Grumpy_Geoff]

I have 5 mounts listed in /etc/auto.network
When I reactivate a mount, I get 5 x command ['/etc/init.d/autofs stop', 'sleep 2', '/etc/init.d/autofs start'] listed in the debug log.

That seems excessive.

Yep - viewtopic.php?f=47&t=12439&p=167256#p167256

[Grumpy_Geoff]

Updated, but get the same results.
8192_0_1_0_0_0_0_0_0_0_20190405133534.jpg

And if you activate mount 'MyMovies' do both shares/bookmarks/symlinks work?
i.e. is there a bug that doesn't issue autofs start when an inactive mount is detected after first stopping the mounts?

[Star6key]

...
Previously you stated it as -
MyTVShows on //192.168.1.120/NonAnime

The screenshot doesn't have MyTVShows.
Have you renamed local share 'MyTVShows' as 'NonAnime' (or vice versa)?
...

And in a later post I said -

...
I even deleted the mount, created a new one (with a different name, and no SymLink), but I see the same behaviour in the the Autofs directory.
...

So MyTvShows is now NonAnime.

edit -
I'll have to get back to this as I've just picked up the U4 from post office, and will be setting that up.

[Grumpy_Geoff]

i.e. is there a bug that doesn't issue autofs start when an inactive mount is detected after first stopping the mounts?

I think that's the issue. I'm guessing if the code sees an inactive mount it just issues an autofs stop, whereas if it sees an active mount it issues an autofs stopt and an autofs start.
If the inactive mount is found last then the network isn't restarted and /media/autofs/ is empty even if active mounts are present.

[Star6key]

i.e. is there a bug that doesn't issue autofs start when an inactive mount is detected after first stopping the mounts?

I think that's the issue. I'm guessing if the code sees an inactive mount it just issues an autofs stop, whereas if it sees an active mount it issues an autofs stopt and an autofs start.
If the inactive mount is found last then the network isn't restarted and /media/autofs/ is empty even if active mounts are present.

Well done GG. That was the problem. Activated MyMovies, inactivated NonAnime, then reactivated it and can now access it.

They should pay you more... oh wait...

Soooooo, a bug??

[prl]

Yes, a bug.

When the changes to the mounts are saved, for each autofs mount it does a /etc/init.d/autofs stop, and then a '/etc/init.d/autofs start if the mount is marked active. This style is correct for the umount/mount commands used for fstab-based mounts, where the command only affects that mount, but wrong for autofs where the autofs start/stop commands affect all autofs mounte.

This explains both the problem that Star6key is seeing, and also the fact that GrumpyGeoff is seeing on stop/start pair for each mounted filesystem on reactivation to the state where all filesystems are active.

What the code should to is flag that a single autofs stop is needed if there are any autofs mounts at all, and then a single autofs start if there are any active autofs mounts.

It may take a bit of thinking about how best to untangle all of this, because the list of filesystems to be checked is iterated through by doing an action with a callback that re-calls the action if there are any more mounts to process. It will probably be just a matter of setting a stop command string if needed and an start command string if needed, and then executing them in sequence when the list of mounts to process has been exhausted.

The workaround is to reboot after any new activations or deactivations of existing mounts, as Star6key has already discovered.

I'll get onto it when I've finished with the zap timer issue.

[Star6key]

Thanks Prl. No need to hurry, now that we know what causes it and how to get around it.

[Grumpy_Geoff]

One workaround (not applicable in all cases) is to make sure that the last mount in the list is always enabled.

What list is that though?
In Star6key's case, the inactive entry was listed first in Mount Viewer screen, but must have been "actioned" last.
Looking at my mounts, the ordering doesn't match between the Mount Viewer screen and /etc/enigma2/automounts.xml file contents.
The contents order of /etc/auto.network does match the order of the active entries from /etc/enigma2/automounts.xml, so perhaps that's the processing order (but not directly user-controllable).

Yes, I know you said "not applicable in all cases".

[prl]

One workaround (not applicable in all cases) is to make sure that the last mount in the list is always enabled.

What list is that though?
In Star6key's case, the inactive entry was listed first in Mount Viewer screen, but must have been "actioned" last.
Looking at my mounts, the ordering doesn't match between the Mount Viewer screen and /etc/enigma2/automounts.xml file contents.
The contents order of /etc/auto.network does match the order of the active entries from /etc/enigma2/automounts.xml, so perhaps that's the processing order (but not directly user-controllable).

Yes, I know you said "not applicable in all cases".

You're right. It's a straightforward iteration, but it's in this order: AutoMount.automounts.keys() (in the networkbrowser code in the enigma-plugins repository). Which is pretty much random order.

I'll remove the suggestion, since it's not possible to tell which will be last in the iteration.

[Grumpy_Geoff]

I'll remove the suggestion, since it's not possible to tell which will be last in the iteration.

Okay, The other work-around would be to delete the mount that was to be inactivated. I guess it depends on the lesser user-impact.

[peteru]

What the code should to is flag that a single autofs stop is needed if there are any autofs mounts at all, and then a single autofs start if there are any active autofs mounts.

No, the code should not make such assumptions. This is a system level service and could be in use (or disabled) by something else. What enigma2 should do is to cause the existing service to reload it's configuration. That's a single call to /etc/init.d/autofs reload after any number of configuration changes.

[prl]

Sounds even better

[prl]

This opened a bit of a can of worms!

Enhancement request #716: [NetworkBrowser] Improvements to default local sharenames (Implementation merged)
Bug #717: [NetworkBrowser] Having disabled automounts can stop the automounter (Fix merged)
Bug #718: [NetworkBrowser] Non-alphanumerics poorly handled in local sharenames (Fix merged)
Bug #719: [NetworkBrowser] "Enigma2 old format" mounts can fail (Not yet fixed, but should be simple to fix - "Enigma2 old format" mounts may be automatically be converted to Enigma2 mounts and the old style mount capability removed)
Bug #720: [NetworkBrowser skin] Cleanups required (Fix merged)
Bug #721: [NetworkBrowser] Wrong mount/unmount logic for enigma2 mounts (Being debugged)

#720 is not required for OverlayHD - those screens are OK in that skin.

None submitted to the repositories yet, but the fixed & tested ones should be in the next few days.

[Star6key]

Love your work Prl.

[prl]

Thanks.

[prl]

Updated the status of the fixes.

[prl]

NetworkBrowser: the gift that keeps on giving - bugs.

See Bug #721 above.

There are also still some small layout niggles in the NetworkBrowser skins that were missed in the first fixup (Bug #720)

[prl]

Perhaps getting slightly off-topic, but sort-of related.

In the NetworkBrowser, there are two icons to display whether a mount is CIFS (SBM) or NFS. The text on them looks hand-drawn (really ugly if you magnify the icons. Here are a couple of alternatives using a font instead of hand-written text.

Old CIFS:

i-smb.png (1.77 KiB) Viewed 3354 times

New CIFS:

i-smb.new.png (9.61 KiB) Viewed 3354 times

Old NFS:

i-nfs.png (1.88 KiB) Viewed 3354 times

New NFS:

i-nfs.new.png (9.02 KiB) Viewed 3354 times

Suggestions for other fonts? One I've looked at is PT Sans Narrow Bold Condensed, which has narrower strokewidth, but more similar character proportions to the original.

Here's an example of the PT Sans (just text):

Screen Shot 2019-04-25 at 16.31.48.png (4.6 KiB) Viewed 3354 times

I have a cleaned-up version of the original icon that I can relatively easily put text alternatives on top of.

If anyone wants to try the icons in context, the i-*.new.png files need to go in /usr/lib/enigma2/python/Plugins/SystemPlugins/NetworkBrowser/icons, renamed to their original names (remember to back up the old files). Then do a GUI restart. To go back, replace the new files with the originals and restart the GUI.

[peteru]

The new icons look good with the font you used. Happy to merge them, if you want to make a pull request.

[prl]

I'm growing to like the PT Sans version better

[sub3R]

I'm growing to like the PT Sans version better

Me too. Just looking at what you posted, not on the Beyonwiz. Is that bold or regular?

[prl]

I'm growing to like the PT Sans version better

Me too. Just looking at what you posted, not on the Beyonwiz. Is that bold or regular?

"PT Sans Narrow Bold Condensed"

[Gully]

Looks great, thanks Peter

[MrQuade]

Can you adjust the colour to be a very dark grey?
When its black it kinda looks like it is just stuck on over the top of the icon (if that make sense).
The hand-drawn font may have been selected so that the text looks like it is part of the icon.