Re: Server seemingly ignoring openvpn connections

Figured it out. Networkmanager requires the auth mode to be TLS with user, not just TLS and key password. It will not prompt the user for a login (at least in gnome shell) but instead just time out. This is contra the official clearos documentation, so someone might want to look into that. The doc also has instructions for a deprecated version of the windows client, which uses a different import and setup method.

Figured it out. Networkmanager requires the auth mode to be TLS with user, not just TLS and key password. It will not prompt the user for a login (at least in gnome shell) but instead just time out. This is contra the official clearos documentation, so someone might want to look into that. The doc also has instructions for a deprecated version of the windows client, which uses a different import and setup method.

Road Warrior setup. The syslog is from the client, the tcpdump is from the server, as is the (empty) message log.

I got my hands on a windows machine and was able to connect just fine via the openvpn client on Windows 10. This seems to be a networkmanager issue.

Server seemingly ignoring connections

I have been trying to set up openvpn through clearos's tools but every attempted connection times out:

syslog:


Connectivity is fine with everything else (SSH, HTTPS) and I checked, both UDP and TCP were automatically added to the incoming firewall. I tried connecting with the client both with the firewall on and allow rules and with the firewall (temporarily, obviously) down. Still nothing. So my next thought was dropped packets

tcpdump -ni enp3s0 udp and port 1194


Nothing there. Considering this is a stock clearos openvpn setup and the client is using the imported .ovpn I am at a complete loss.

Re: Zarafa throwing sql errors

Figured it out; there were a bunch of core dumps sitting around from the last time zarafa acted up, and the system slowly strangled itself with the reduced space.

Incidentally, while SQL isn't on root, it does require space on root for transactions.

Figured it out; there were a bunch of core dumps sitting around from the last time zarafa acted up, and the system slowly strangled itself with the reduced space.

Incidentally, while SQL isn't on root, it does require space on root for transactions.

Zarafa throwing sql errors

Some time last night our mail system stopped responding (ClearOS 6.8, Zarafa 7.1.5). The webapp loads, but any time it attempts to retrieve information from the server it gives an error, "could not load the contents of this folder," and we are no longer receiving push notifications. I tried stopping and restarting the zarafa services, and all stop and restart appropriately. Zarafa's services have not been touched in months and the only modifications to this system were the monthly antispam and antimalware updates last week.

The only error I can find is in the server.log:



Error 28 is a space error, so I checked the partitions:



Which seems like it would be cause for alarm, but it was my understanding was that the sql system lived on data0 and not root, and that 492k would be large enough for an sql query in any case. Am I incorrect in that assumption? Is this a zarafa-specific issue? If it is an issue with the space on root, what is the best way to clear or add space?