[Dxspider-support] Help request - unable to save user settings

Michael Carper, Ph.D. mike at wa9pie.net
Sat Sep 14 23:28:20 CEST 2019


For a year now, I've been trying to sort this out. It's a complete mystery.
Anyone have any new ideas?

[image: image.png]

Mike, WA9PIE
WA9PIE-2; dxc.wa9pie.net; port 8000

On Tue, Jan 29, 2019 at 11:28 AM Michael Carper, Ph.D. <mike at wa9pie.net>
wrote:

> I think these are good:
>
> [sysop at instance-5 ~]$ findmnt
> TARGET                       SOURCE        FSTYPE      OPTIONS
> /                            /dev/sda1     ext4
> rw,relatime,seclabel,barrier=1,data=ordered
> ├─/proc                      proc          proc        rw,relatime
> │ ├─/proc/bus/usb            /proc/bus/usb usbfs       rw,relatime
> │ └─/proc/sys/fs/binfmt_misc               binfmt_misc rw,relatime
> ├─/sys                       sysfs         sysfs       rw,relatime,seclabel
> ├─/selinux                                 selinuxfs   rw,relatime
> └─/dev                       devtmpfs      devtmpfs
> rw,relatime,seclabel,size=1819664k,nr_inodes=454916,mode=7
>   └─/dev                     devtmpfs      devtmpfs
> rw,relatime,seclabel,size=1819664k,nr_inodes=454916,mode=7
>     ├─/dev/pts               devpts        devpts
> rw,relatime,seclabel,gid=5,mode=620,ptmxmode=000
>     └─/dev/shm               tmpfs         tmpfs
>  rw,relatime,seclabel,size=1832216k,nr_inodes=458054
>
> On Tue, Jan 29, 2019 at 5:05 AM Dirk Koopman via Dxspider-support <
> dxspider-support at tobit.co.uk> wrote:
>
>> Also do a 'findmnt' and check that the volume that holds the / partition
>> (or /home if you have separate volumes for these) is 'rw' and not 'ro'.
>>
>> djk at dirk6:~/Desktop$ findmnt
>> TARGET                                SOURCE      FSTYPE     OPTIONS
>> /                                     /dev/sdc1   ext4       rw
>> ,relatime,errors=remount-ro,data=ordered
>> ├─/sys                                sysfs       sysfs
>> rw,nosuid,nodev,noexec,relatime
>> │ ├─/sys/kernel/security              securityfs  securityfs
>> rw,nosuid,nodev,noexec,relatime
>> │ ├─/sys/fs/cgroup                    tmpfs       tmpfs
>> ro,nosuid,nodev,noexec,mode=755
>> │ │ ├─/sys/fs/cgroup/systemd          cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/
>> │ │ ├─/sys/fs/cgroup/cpuset           cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,cpuset
>> │ │ ├─/sys/fs/cgroup/net_cls,net_prio cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,net_cls,net_prio
>> │ │ ├─/sys/fs/cgroup/memory           cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,memory
>> │ │ ├─/sys/fs/cgroup/rdma             cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,rdma
>> │ │ ├─/sys/fs/cgroup/cpu,cpuacct      cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,cpu,cpuacct
>> │ │ ├─/sys/fs/cgroup/devices          cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,devices
>> │ │ ├─/sys/fs/cgroup/pids             cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,pids
>> │ │ ├─/sys/fs/cgroup/freezer          cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,freezer
>> │ │ ├─/sys/fs/cgroup/blkio            cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,blkio
>> │ │ ├─/sys/fs/cgroup/perf_event       cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,perf_event
>> │ │ └─/sys/fs/cgroup/hugetlb          cgroup      cgroup
>> rw,nosuid,nodev,noexec,relatime,hugetlb
>> │ ├─/sys/fs/pstore                    pstore      pstore
>> rw,nosuid,nodev,noexec,relatime
>> │ ├─/sys/kernel/debug                 debugfs     debugfs    rw,relatime
>> │ ├─/sys/fs/fuse/connections          fusectl     fusectl    rw,relatime
>> │ └─/sys/kernel/config                configfs    configfs   rw,relatime
>> ...
>> ...
>> ├─/home                               /dev/md0    ext4       rw
>> ,noatime,stripe=256,data=ordered
>> ...
>>
>>
>>
>> Dirk
>> On 29/01/2019 08:03, dd5xx--- via Dxspider-support wrote:
>>
>> Hello Mike,
>>
>> please check also the permissions on file system level at the top
>> directory with "ls -ldh ../data". The directory needs an execution
>> permission bit. You might wonder: why won’t the write permission work
>> without an execute permission on the directory? This is because of the fact
>> that you can only retrieve the permissions of a directory when its execute
>> bit is set. If it is not set, the OS won’t know whether it actually has the
>> write permission.
>>
>> About the filter settings, they are saved in /spider/filter/spots for
>> each user as a file "username.pl" so in my case in that directory I see
>> files like DD5XX.pl, KE4KY-1.pl, and so on ... you could also check those
>> files and the directory permission /spider/filter
>>
>> The permissions on my file system looks like that:
>>
>> ls -ldh /spider/filter/spots
>> drwx------ 2 foo users 4.0K Jan  9 14:47 /spider/spots/
>>
>> ls -ldh /spider/data
>> drwx------ 7 foo users 4.0K Jan 23 01:01 /spider/data/
>>
>> But maybe it's something quite different and some other users will reply
>> to your question, too. Hope you get this issue fixed soon. Good luck and
>> all the best.
>>
>> 73
>> Saki, DD5XX
>>
>>
>> *Gesendet:* Dienstag, 29. Januar 2019 um 08:43 Uhr
>> *Von:* "Michael Carper, Ph.D. via Dxspider-support"
>> <dxspider-support at tobit.co.uk> <dxspider-support at tobit.co.uk>
>> *An:* "The DXSpider Support list" <dxspider-support at dxcluster.org>
>> <dxspider-support at dxcluster.org>
>> *Cc:* "Michael Carper, Ph.D." <mike at wa9pie.net> <mike at wa9pie.net>
>> *Betreff:* [Dxspider-support] Help request - unable to save user settings
>> Since sometime last fall, users making connection to my cluster
>> (WA9PIE-2) have been unable to save settings.  So every time the user
>> connects, they are greeted with:
>>
>> Please enter your name, set/name <your name>Please enter your QTH,
>> set/qth <your qth>Please enter your location with set/location or set/qraPlease
>> enter your Home Node, set/homenode <your home DX Cluster>WA9PIE de
>> WA9PIE-2 29-Jan-2019 0739Z dxspider >
>>
>> In addition, users can't save filters (which, for the 800 - 1000 users
>> that connect here, this is a significant problem).
>>
>> I've tried some things and haven't been successful.  The permissions are
>> correct.
>>
>> [image: image.png]
>>
>> Has anyone seen this happen before?  Does anyone know of a way to fix it?
>>
>> At this point, the users.v3 file is complete rubbish and unimportant
>> (since it's not retaining anything anyway).
>>
>> If anyone has any ideas, please let me know.
>>
>> Mike, WA9PIE
>> _______________________________________________ Dxspider-support mailing
>> list Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>> _______________________________________________
>> Dxspider-support mailing listDxspider-support at tobit.co.ukhttps://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20190914/08e4eb93/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mcghplknhhapdcml.png
Type: image/png
Size: 26294 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20190914/08e4eb93/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 28612 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20190914/08e4eb93/attachment-0003.png>


More information about the Dxspider-support mailing list