protocol version mismatch — is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(174) [sender=3.1.0]
Are you trying to rsync to a valid shell user?
protocol version mismatch — is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(174) [sender=3.1.0]
Are you trying to rsync to a valid shell user?
If we are just allowing both on AllowUsers in file /etc/ssh/sshd_config, new users won’t be allowed to access the server.
So!, lets edit it a add the new user. Find AllowUser line and add it there.
sudo nano /etc/ssh/sshd_config
This should look something like
#PermitRootLogin without-password PermitRootLogin no StrictModes yes AllowUsers bofh newuser
Save and Exit!
Restart SSH
service ssh restart
Now the user!
addgroup --system filetransf usermod -G filetransf username chown root:root /home/username chmod 755 /home/username cd /home/username chown username:filetransf *
Hooray!
SysAdminBoard is a simple dashboard system written in Python, HTML and Javascript and served on a simple CherryPy Webserver (included). It was originally written to reformat snmp data for the Panic Statusboard iPad App, but has since become a fully stand-alone project that can grab data from a variety of sources and render charts and graphs in a web browser.

Usefull!
cat /path/access.log | awk '{print $1}' | sort -n | uniq -c | sort -nr | head -50
[root@sd-8XXX pjrf]# /usr/local/sbin/certbot-auto renew >> /var/log/le-renew.log Saving debug log to /var/log/letsencrypt/letsencrypt.log Cert not yet due for renewal Cert not yet due for renewal Cert not yet due for renewal Cert not yet due for renewal [root@sd-8XXX pjrf]# [root@sd-8XXX pjrf]# /usr/local/sbin/certbot-auto renew --force-renew
In our /etc/httpd/conf/httpd.conf lets see if we have the following lines on it.
Uncomment them or add them.
LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_balancer_module modules/mod_proxy_balancer.so LoadModule proxy_http_module modules/mod_proxy_http.so # Uncomment these to proxy FTP or HTTPS #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so #LoadModule proxy_connect_module modules/mod_proxy_connect.so
[Thu Mar 09 02:23:43.435879 2017] [cgi:error] [pid 28444] [client 94.63.XXX.XXX:54192] AH01215: Can’t locate CGI/Carp.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /path/to/cgi/admin/admin.cgi line 31.
This solved my issue…
yum install perl-CGI
[Thu Mar 09 02:26:54.892385 2017] [cgi:error] [pid 28442] [client 94.63.XXX.XXX:54242] AH01215: [Thu Mar 9 02:26:54 2017] admin.cgi: [Thu Mar 9 02:26:54 2017] admin.cgi: Can’t locate LWP/Simple.pm in @INC (@INC contains: /path/to/cgi/admin/ /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at ./shared/subs3.pm line 1003.
[Thu Mar 09 02:26:54.892456 2017] [cgi:error] [pid 28442] [client 94.63.XXX.XXX:54242] AH01215: [Thu Mar 9 02:26:54 2017] admin.cgi: [Thu Mar 9 02:26:54 2017] admin.cgi: BEGIN failed–compilation aborted at ./shared/subs3.pm line 1003.
[Thu Mar 09 02:26:54.892599 2017] [cgi:error] [pid 28442] [client 94.63.XXX.XXX:54242] AH01215: [Thu Mar 9 02:26:54 2017] admin.cgi: Compilation failed in require at /path/to/cgi/admin/admin.cgi line 151.
This solved my issue!
yum install perl-XML-Simple
While I was trying to update a CentOS server…
I got an error saying that /bott/ didn’t had enough disk space……
Sumário de erros ------------- Requisitos de disco: São precisos pelo menos mais 30MB de espaço livre no sistema de ficheiros /boot.
I’v followed the following instructions http://unix.stackexchange.com/a/105029/65996 and it worked!
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: subdomain.domain.com
Type: unauthorized
Detail: Invalid response from
http://subdomain.domain.com/.well-known/acme-challenge/XXXXXXX_XXXXXXXX:
"<!DOCTYPE html>
<html lang="en">
<head>
<title>404 Page Not Found</title>
<style type="text/css">
::selection{ background-color"
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address.
Try to add the following, inside server{}, on user nginx domain configuration..
location /.well-known/acme-challenge/ {
try_files $uri /dev/null =404;
}
And reboot nginx… 🙂