Marc's questions

We have 4 (presumably) identical Ubuntu 20.04 machines and one of them expects the environment variables HTTP_PROXY, HTTPS_PROXY AND NO_PROXY to be lower case.

Programs such as curl and apt work perfectly on all servers but the one. When we switch HTTP_PROXY to http_proxy etc that strange server is happy. Before that apt and curl don't see the proxy.

None of the other servers have the lower case versions of these variables.

• What could be the reason that one server expects lower case?
• What could be the reason that all other servers work with lower case?

I installed dwm but cannot get it to display on the Ubuntu 20.04 (Gnome) login screen. I added the desktop file to /usr/share/xsessions. I also deleted the i3 with debug option from this directory but it still appears. Reboot does not help.

The login page seems to ignore /usr/share/xsessions - is there something else I need to do?

/usr/share/xsessions/dwm.desktop

[Desktop Entry]
Name=DWM
Comment=DWM
Exec=dwm
Icon=dwm
Type=XSession

As user1 (primary group root) on server1 (Linux) I am able to write files to /tmp.

The permissions are:

drwxrwxrwt  19 root              root  4096 Jan  3 11:04 ./

When I mount (cifs) server1 using usern=user1 on server2 (Linux) I am unable to write any files.

user2@server2$ echo hello >> /mnt/server1/tmp/foo
-bash: /mnt/server2/tmp/foo: Permission denied

However, I am able to write files from a Windows client when I connect with user1!

/etc/samba/smb.conf on server1

[root]
        comment = Root
        available = yes
        path = /
        write list = root user1 @root
        read only = no
        browsable = yes
        public = yes
        writable = yes

/etc/fstab on server2

//server1/root    /mnt/server1   cifs    user=user1,password=***,dir_mode=0770,file_mode=0770,nounix    ,uid=0,gid=0,forceuid,forcegid

I have tried with/without the uid=0,gid=0,forceuid,forcegid options as well as the mode and nounix options.

From server2I can list files in /mnt/server1/tmp and see files I created locally on server1. I don't see any permissions errors in the logs /var/log/*.

Where/how can I diagnose the issue?

UPDATE

I am able to write to the share from server2 as root. This is really strange as I would think server1 would not trust that root from server2 is the same root on server1.

When we re-deploy an application we use systemd restart to restart the application. It would seem that either systemd restart or systemd status (or both) are unreliable.

1. Sometimes systemd restart DOESN'T restart the application and doesn't throw an error. PID is the same as before and the old version of the app is still running. Is restart effective immediately?
2. Sometimes systemd restart does kill the old process and start the new process but systemd status shows the service as dead. We see the process running as a child of systemd.

As an example of the 2nd problem: systemctl status is says the service inactive(dead) but it's definitely running (new pids 25548 and 25551)!

$systemctl status gateway.service
gateway.service - The API Gateway - Nginx
   Loaded: loaded (/etc/systemd/system/gateway.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Wed 2020-08-05 14:00:16 CEST; 1h 43min ago
  Process: 25545 ExecStart=/usr/sbin/nginx -c /prg/nginx/conf/gateway.conf (code=exited, status=0/SUCCESS)
  Process: 25542 ExecStartPre=/usr/sbin/nginx -t -c /prg/nginx/conf/gateway.conf (code=exited, status=0/SUCCESS)
  Process: 25540 ExecStartPre=/usr/bin/rm -f /daten/nginx.pid (code=exited, status=0/SUCCESS)
 Main PID: 25545 (code=exited, status=0/SUCCESS)
    Tasks: 2
   Memory: 130.0M
   CGroup: /system.slice/gateway.service
           ├─25548 nginx: master process /usr/sbin/nginx -c /prg/nginx/conf/gateway.conf
           └─25551 nginx: worker process

ps | grep nginx shows the 2 nginx processes:

nginx      25548              root    5u  IPv4 58124367      0t0  TCP *:8080 (LISTEN)
nginx      25551             nginx    5u  IPv4 58124367      0t0  TCP *:8080 (LISTEN)

pstree shows these 2 processes as children of systemd:

systemd─┬...
        ├─nginx───nginx

systemd Config

[Service]
Type=forking
PIDFile=/daten/nginx.pid

# Nginx will fail to start if /run/nginx.pid already exists but has the wrong
# SELinux context. This might happen when running `nginx -t` from the cmdline.
# https://bugzilla.redhat.com/show_bug.cgi?id=1268621
ExecStartPre=/usr/bin/rm -f /daten/nginx.pid
ExecStartPre=/usr/sbin/nginx -t -c /prg/nginx/conf/gateway.conf
ExecStart=/usr/sbin/nginx  -c /prg/nginx/conf/gateway.conf

KillSignal=QUIT
TimeoutStopSec=5
KillMode=process
PrivateTmp=true

Ubuntu 20.04 has decided we need 4 clicks to shut down:

1. Click top right of screen arrow-down
2. Expand "power off/logout" panel
3. Click "Power off"
4. Confirm you want to power off by choosing power off vs reboot etc

Let's cut out at least 2 clicks here... how?

UPDATE: This is a "Lounge PC" - operated by mouse (no power button within reach as the laptop is closed). We watch a film, we want to click to shutdown and not type commands.