sme 10 uses systemd , no sysvinit anymore. service command is deprecated.
you should use
systemctl restart rsyslog.service
You will think, yes but it did restart the service using my old command, because it will be redirected to systemd, but you need to be aware of that to understand that old how to might brake because the startup script is different
now what is in this script
systemctl cat rsyslog.service
# /usr/lib/systemd/system/rsyslog.service
[Unit]
Description=System Logging Service
;Requires=syslog.socket
Wants=network.target network-online.target
After=network.target network-online.target
Documentation=man:rsyslogd(8)
Documentation=http://www.rsyslog.com/doc/
[Service]
Type=notify
EnvironmentFile=-/etc/sysconfig/rsyslog
ExecStart=/usr/sbin/rsyslogd -n $SYSLOGD_OPTIONS
Restart=on-failure
UMask=0066
StandardOutput=null
Restart=on-failure
[Install]
WantedBy=multi-user.target
;Alias=syslog.service
# /usr/lib/systemd/system/rsyslog.service.d/51koozali.conf
[Install]
WantedBy=sme-server.target
so /etc/sysconfig/rsyslog is still in use
$SYSLOGD_OPTIONS is still in use but looking at both the man rsyslogd pages of sme 9 and 10 i can not find reference to -r and -m options
i see two things..
is your server trying to log something on its local interface or external? if external rhe firewall is preventing that.
other wise this is simply that now you should use the config file to do that. seems that it was a deprecated option still working in centos 6 but not documented and removed on centos 7
see
https://linuxhint.com/send_linux_logs_remote_server/. this is written for debian , but options should be similar and you just have to template the changes
and update the wiki