No Shares management from Dashboard

[carloph]

In my RAID6 NAS, I need to add/delete some Shared areas.

Currently I can login as Admin and access the Dashboard.

From the main Dashboard panel, I can access all icons/functions, out of the SHARE one.

The main panel correctly indicates the presence of "28 Shares", but when I click on the SHARE icon, a warning msg appears saying "Your device is offline. Please verify your network connection." :shock:

NOTE: from the File Browser window I can access the shared directories

Here is the MESSAGE log file, downloaded from the Dashboard Support panel

Message log file

Thanks for any help

[fvdw]

lacie firmware ?

[carloph]

Yes, updated to the last version available

[fvdw]

Then I can not give much advice as I don't use it. We have developed our own (fvdw-sl). Seems some services are not running on your device.

from the File Browser window I can access the shared directories

But can you also upload and download files?

Do you have ssh acces to your nas ?

[carloph]

Unfortunately I cannot install your fvdw-sl

I can Browse/upload/download files in the shared directories through the Lacie HCI

I can access the NAS thorugh SFTP

I can access the NAS through SSH

Thanks

[fvdw]

Funny, if all that works normally I would guess there is something wrong in the files used for the webinterface or settings of the web interface. The last point is more likely as all functions work except the shares button. I do not know if the lacie 'dashboard" has the possibility to grant access to "normal" users which have then less privileges then "admin" webinterface. Such normal user will not be allowed to create new shares and users I would expect. So how do you login to the dashboard and do you have admin right ?


PS if you can access your nas via ssh then you can use Putty or winScp to connect to your nas and investigate whats going on.
Putty is more for investigation via command line winSCP easier to browse directories and view content of files or correct them

If you connect with winscp you could look for the system log (normal stored under name "messages" in /var/log but lacie may have done it different). Look in the system log for any clues.

[fvdw]

I downloaded your message log

Are you using the nfs server ?

There are some problems with that according your lo, maybe the "offline" message is related to that

rpc server down and failures of NFSD

Code: Select all

Feb 26 08:56:20 LACIE5BIG2 last message repeated 20 times
Feb 26 08:56:38 LACIE5BIG2 last message repeated 6 times
Feb 26 08:56:41 LACIE5BIG2 ipcommd: Connection to Unicorn Dbus service failed
Feb 26 08:56:41 LACIE5BIG2 ipcommd: RPC server down
Feb 26 08:56:41 LACIE5BIG2 ipcommd: stop
Feb 26 09:04:29 LACIE5BIG2 avahi-daemon[3517]: Invalid query packet.
Feb 26 09:04:37 LACIE5BIG2 avahi-daemon[3517]: Invalid query packet.
Feb 26 09:18:15 LACIE5BIG2 afpd[3688]: AFP/TCP started, advertising 172.25.3.234:548 (2-2-1-p6)
exporting *:/shares/Name1
....... Exporting all 28 Shares .......
exporting *:/shares/Name28
Feb 26 09:18:21 LACIE5BIG2 rpc.mountd[3702]: Kernel does not have pseudo root support.
Feb 26 09:18:21 LACIE5BIG2 rpc.mountd[3702]: NFS v4 mounts will be disabled unless fsid=0
Feb 26 09:18:21 LACIE5BIG2 rpc.mountd[3702]: is specfied in /etc/exports file.
Feb 26 09:18:21 LACIE5BIG2 rpc.mountd[3703]: Version 1.2.3 starting
Feb 26 09:18:21 LACIE5BIG2 rpc.statd[3707]: Version 1.2.3 starting
Feb 26 09:18:21 LACIE5BIG2 rpc.statd[3707]: Flags:
Feb 26 09:18:22 LACIE5BIG2 rpc.statd[3707]: Running as root.  chown /var/lib/nfs to choose different user
Feb 26 09:18:22 LACIE5BIG2 sm-notify[3716]: Version 1.2.3 starting
Feb 26 09:18:22 LACIE5BIG2 kernel: [ 1732.960000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Feb 26 09:18:22 LACIE5BIG2 kernel: [ 1732.960000] NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
Feb 26 09:18:22 LACIE5BIG2 kernel: [ 1732.960000] NFSD: starting 90-second grace period
Feb 26 09:18:47 LACIE5BIG2 kernel: [ 1757.920000] warning: `proftpd' uses 32-bit capabilities (legacy support in use)
Feb 26 09:18:47 LACIE5BIG2 proftpd[3753]: 172.25.3.234 - ProFTPD 1.3.3d (maint) (built Fri May 29 2015 20:31:47 UTC) standalone mode STARTUP
Feb 26 09:19:01 LACIE5BIG2 proftpd[3753]: 172.25.3.234 - ProFTPD killed (signal 15)
Feb 26 09:19:01 LACIE5BIG2 proftpd[3753]: 172.25.3.234 - ProFTPD 1.3.3d standalone mode SHUTDOWN
Feb 26 09:19:02 LACIE5BIG2 proftpd[3760]: 172.25.3.234 - ProFTPD 1.3.3d (maint) (built Fri May 29 2015 20:31:47 UTC) standalone mode STARTUP
Feb 26 09:19:10 LACIE5BIG2 kernel: [ 1780.820000] iSCSI Enterprise Target Software - version 1.4.20.2
Feb 26 09:19:10 LACIE5BIG2 kernel: [ 1780.820000] iscsi_trgt: Registered io type fileio
Feb 26 09:19:10 LACIE5BIG2 kernel: [ 1780.820000] iscsi_trgt: Registered io type blockio
Feb 26 09:19:10 LACIE5BIG2 kernel: [ 1780.820000] iscsi_trgt: Registered io type nullio
Feb 26 09:20:07 LACIE5BIG2 avahi-daemon[3517]: Invalid query packet.
Feb 26 09:20:47 LACIE5BIG2 last message repeated 7 times
Feb 26 09:27:48 LACIE5BIG2 avahi-daemon[3517]: Invalid query packet.

You could try to disbale nfs server and reboot

[fvdw]

Feb 26 08:56:41 LACIE5BIG2 ipcommd: Connection to Unicorn Dbus service failed

This means there is a problem with service unicorn, unicorn controls all action on your nas. Not clear yet what the problem is.

You could connect with putty and give on the command line this command and see if it gives relevant information

Code: Select all

systemctl status unicorn.service

can be that you have to use capital for unicorn

Code: Select all

systemctl status Unicorn.service

[carloph]

Thanks for your kind reply

I have admin right

I made a mistake: I do not have SSH access (only SFTP)

I've already accessed the /var/log DIR, the file I sent was the /var/log/messages.

The unicorn.log can be downloaded here:

Unicorn.log

I can disable NFS from the Lacie Dashboard
Doubt (from a non-expert user): if I disable NFS, share will continue to be active ? NFS is used by the Sharing service or not ?

thanks

[carloph]

I disabled NFS, restarted the NAS, but the sharing problem remains