Good morning All
Continuing on the topic of Avance-3 with TopSpin-3.7.0 (Alma-9.2):
Activating the tftp socket ("active" and "listening", persistent after
reboot) did not help with "cf" failing to communicate with the acquisition system.
Rebooting the IPSO *via* the web interface resulted in a loss of
communication with the browser but following the IPSO reboot, "cf" succeeded.
In TopSpin-2.1pl6, the IPSO is addressed as 149.236.99.254 but in
TopSpin-3.7.0, the IPSO is addressed as 149.236.99.10.
The IPSO reboot seems to have fixed the address issue and the system is
operational.
On the topic of the sticky bit:
In Alma-9, the permissions on "/tmp" are "drwxrwxrw*t.*" - sticky bit "t"
and a stop "." at the end.
In RHEL-4, the permissions on "/tmp" are "drwxrwxrw*t*" - sticky bit "t"
but no stop "." at the end.
The stop "." indicates some kind of extra security.
In TS-3.7, ICON-NMR ATMA operations fail with the error "*wobbrout : Error
in ipsoprep(): gotst: System Error 3 when opening /tmp/_tcon1: Permission
denied*". Unsetting the sticky bit fixes the problem (as John mentioned)
but some web searching indicates that this is not to be recommended. In
TS2.1, ICON-NMR ATMA operations are successful, even with the sticky bit.
Comparing the two OS's permissions on "/tmp" seems to suggest that the
problem is not necessarily the sticky bit itself but something to do with
the extra security and the ownership of the TopSpin stuff in "/tmp". I see
on my Alma-9 system that SELinux is "enabled" and "enforcing" and that
"_tcon1" is owned by "nmrsu" so perhaps the problem is that SELinux is
denying access to "_tcon1" while using TopSpin as another user.
Kind regards,
Craig.
On Fri, 3 May 2024 at 21:57, John Decatur via groups.io <jdd13=
columbia.edu_at_groups.io> wrote:
> My IPSO on my AVIII still boots and the workstation has not been rebooted
> for over a week. All I did was enable tftp and the statuses of the relevant
> processes are:
>
> systemctl status tftp.socket
> â tftp.socket - Tftp Server Activation Socket
> Loaded: loaded (/usr/lib/systemd/system/tftp.socket; enabled; preset:
> disabled)
> Active: active (listening) since Mon 2024-04-15 10:51:12 EDT; 2 weeks
> 3 days ago
> Until: Mon 2024-04-15 10:51:12 EDT; 2 weeks 3 days ago
> Triggers: â tftp.service
> Listen: [::]:69 (Datagram)
> Tasks: 0 (limit: 97997)
> Memory: 4.0K
> CPU: 230us
> CGroup: /system.slice/tftp.socket
>
> Apr 15 10:51:12 nmr29.chem.columbia.edu systemd[1]: Listening on Tftp
> Server Activation Socket.
> [root_at_nmr29 decatur]# systemctl status tftp
> â tftp.service - Tftp Server
> Loaded: loaded (/usr/lib/systemd/system/tftp.service; indirect;
> preset: disabled)
> Active: inactive (dead)
> TriggeredBy: â tftp.socket
> Docs: man:in.tftpd
>
>
> On May 3, 2024, at 10:20 AM, Craig Grimmer <craig.grimmer_at_gmail.com>
> wrote:
>
> A correction of my earlier message:
>
> tftp is installed on Alma-9.2/TS-3.7.0.
>
> Further investigation:
>
> The status of the service is "inactive" (systemctl status tftp / systemctl
> status tftp.socket). This is the same status as my working and currently
> acquiring Centos-7/TS-3.6.5 host computer on another spectrometer. Further
> investigation next week following the suggestions in the thread.
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#1234): https://urldefense.com/v3/__https://ammrl.groups=
.io/g/main/message/1234__;!!PvDODwlR4mBZyAb0!UqyvfzfgOqo4fafY3nRZgm9C2HxrPl=
ynWx1BPE-NCEnLS-weRZ1DrPVXB-QmRXAA6oez1ftV5KhNxdpCD_F75A$
Mute This Topic: https://urldefense.com/v3/__https://groups.io/mt/105862048=
/7559972__;!!PvDODwlR4mBZyAb0!UqyvfzfgOqo4fafY3nRZgm9C2HxrPlynWx1BPE-NCEnLS=
-weRZ1DrPVXB-QmRXAA6oez1ftV5KhNxdqDzUYg0w$
Group Owner: main+owner_at_ammrl.groups.io
-=-=-=-=-=-=-=-=-=-=-=-
Received on Fri May 10 2024 - 02:32:55 MST