Questions[landscape](server)

I have Landscape installed with a self-signed certificate and my own Certificate Authority. I have the CA certificate installed in my browser, and I can access the Landscape website at https://landscape.sahfos.dev/ without TLS issues.

On a client machine, geoserver.sahfos.dev, I have the CA cert installed into /etc/ssl/certs/, and hashed, and

$ openssl s_client -CApath /etc/ssl/certs/ -connect landscape.sahfos.dev:443
...
Verify return code: 0 (ok)

works, as does

$curl https://landscape.sahfos.dev/message-system
Landscape message server

However,

$ sudo landscape-config --computer-title "Geoserver.sahfos.dev" \
--account-name standalone \
--url https://landscape.sahfos.dev/message-system \
--ping-url http://landscape.sahfos.dev/ping --silent

fails.

$ sudo tail -n 12 /var/log/landscape/broker.log
2016-05-05 16:48:41,817 INFO     [MainThread] Starting urgent message exchange with https://landscape.sahfos.dev/message-system.
2016-05-05 16:48:41,822 ERROR    [PoolThread-twisted.internet.reactor-1] Error contacting the server at https://landscape.sahfos.dev/message-system.
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/landscape/broker/transport.py", line 71, in exchange
    message_api)
  File "/usr/lib/python2.7/dist-packages/landscape/broker/transport.py", line 45, in _curl
    headers=headers, cainfo=self._pubkey, curl=curl))
  File "/usr/lib/python2.7/dist-packages/landscape/lib/fetch.py", line 109, in fetch
    raise PyCurlError(e.args[0], e.args[1])
PyCurlError: Error 77:
2016-05-05 16:48:41,822 INFO     [MainThread] Message exchange failed.
2016-05-05 16:48:41,823 INFO     [MainThread] Message exchange completed in 0.01s.

That error 77 indicates a problem with the certificate chain, yet curl doesn't have a problem itself.

Does anybody understand why the client can't establish a secure link to the server?

I'm running something of a bare-bones server (based on Ubuntu 11.04) on an Amazon EC2 micro instance, whose purpose is simply to coordinate the activities of a few webservers. The machine ran well for a few weeks, but now is hanging frequently with its CPU redlined at 100%.

I logged into the machine over SSH and ran a top, which revealed that the landscape-sysinfo process was the perpetrator consuming all of the system resources. A pstree revealed where it was situated:

init─┬─atd
     ├─cron
     ├─dhclient3
     ├─dovecot─┬─2*[dovecot-auth]
     │         ├─3*[imap-login]
     │         └─3*[pop3-login]
     ├─6*[getty]
     ├─master─┬─pickup
     │        └─qmgr
     ├─mountall
     ├─mysqld───11*[{mysqld}]
     ├─rsyslogd───3*[{rsyslogd}]
     ├─sshd─┬─sshd───sshd───bash
     │      ├─sshd───sshd───bash───top
     │      ├─sshd───sshd───bash───pstree
     │      └─sshd───sh───run-parts───50-landscape-sy───landscape-sys+
     ├─udevd───2*[udevd]
     ├─upstart-socket-
     ├─upstart-udev-br
     └─vsftpd

The offending process is listed here as the last child of sshd. If I manually kill landscape-sysinfo, the machine returns to normal - until the process spontaneously respawns, usually a few moments later. (I can "vouch for" the other sshd processes in the above tree. They were legitimate.)

I have no idea why landscape-sysinfo is spawning itself randomly. I doubly have no idea why it's the child of sshd.

I'm obviously none too thrilled about having an SSH processes running on my machine that I can't account for. Initially I feared a breach/trojan/backdoor, so I ran chkrootkit and rkhunter, but they both came up clean.

Does anybody have any idea what could be causing this process to run wild? Any thoughts on how to stop it from respawning?

I have a free account of landscape with 2 servers registered. One of them was replaced with a new one because serious hardware problems. When the new server was online and ready to replace tall functionality, the old server was shutdown and retired, but it still appears in the registered machines, and keeps sending warnings. How can this server be unregistered?