Nagios Support Forum

What is the problem you're trying to resolve? What are the symptoms?
Since the word parasitic is meaningless in this context, I'll guess you mean the strange character in the perfdata output.
If restarting the agent resolves the issue maybe share what agent you use.

Read the error lines in the posted output and resolve the issues.
You are allowed to copy the messages to the clipboard, then paste them into a search and... search. Then you read... Life is easier than you think

Use grep on the config files. Rocket science.
Learn a bit how the system works, then use it. If grep is outside your understanding, study the OS or shell.

If you're using a proxy to get to the internet and it isn't defined right in nagios, the update check will fail.

Nagios sets service/host status based on the return value (0-3) of the check plugin. The text output is meaningless to the alert status.
You can edit the plugin if it's a script, or edit the source and recompile if it's a binary. You could use the negate command to change critical text to fatal.

Looks like the SSL settings don't match and requests have arguments which are not allowed the way nrpe is configured. May 29 10:52:50 dennaglab1.jeppesen.com nrpe[13189]: Error: (!log_opts) Could not complete SSL handshake with 10.16.2.205: 1 May 29 10:53:09 dennaglab1.jeppesen.com nrpe[13191]: Erro...

Follow the upgrade instructions. It's pretty simple.
If you want support, open a case.

If you reset the admin password you should be able to log in to the gui as nagiosadmin. This has no impact on the shell login.

That isn't adding any info.

Change the original valur back to 60 and start over.