I installed sendmail on my Fedora 21 Server installation but when I start it and check it's status I get the following:
[root#localhost mail]# systemctl status sendmail
● sendmail.service - Sendmail Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/sendmail.service; enabled)
Active: failed (Result: resources) since Thu 2015-06-04 11:23:31 CEST; 2min 39s ago
Process: 31776 ExecStart=/usr/sbin/sendmail -bd $SENDMAIL_OPTS $SENDMAIL_OPTARG (code=exited, status=0/SUCCESS)
Process: 31766 ExecStartPre=/etc/mail/make aliases (code=exited, status=0/SUCCESS)
Process: 31763 ExecStartPre=/etc/mail/make (code=exited, status=0/SUCCESS)
Jun 04 11:23:31 localhost.localdomain sendmail[31776]: -bd is not supported by sSMTP
Jun 04 11:23:31 localhost.localdomain systemd[1]: Failed to start Sendmail Mail Transport Agent.
Jun 04 11:23:31 localhost.localdomain systemd[1]: Unit sendmail.service entered failed state.
Jun 04 11:23:31 localhost.localdomain systemd[1]: sendmail.service failed.
What is the problem here? I thought the -bd is not supported by sSMTP was a hint. But I can't find anything on this either.
sSMTP is a send-only sendmail emulator. It does not support -bd option when run as a daemon (see "man ssmtp"). Current sendmail in F21 is an alias to ssmtp. You need to remove ssmtp entirely from F21 (yum erase sSMTP).
Related
I'm not sure why it isn't starting or why its preventing me from connecting, i get this error:
root#vmi: "# sudo service ssh status
ssh.service OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2022-11-27 09:47:47 CST; 4min 58s ago
Docs: man: sshd (8) man: sshd_config(5)
Process: 446 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255/EXCEPTION)
Nov 27 09:47:47 vmi.contaboserver.net systemd[1]: ssh.service: Scheduled restart job, restart>
Nov 27 09:47:47 vmi.contaboserver.net systemd[1]: Stopped OpenBSD Secure Shell server.
Nov 27 09:47:47 vmi.contaboserver.net systemd[1]: ssh.service: Start request repeated too qui>
Nov 27 09:47:47 vmi.contaboserver.net systemd[1]: ssh.service: Failed with result 'exit-code'.
Nov 27 09:47:47 vmi.contaboserver.net systemd[1]: Failed to start OpenBSD Secure Shell server. lines 1-12/12 (END)
Please provide more precise log information, just restart sshd service then use journalctl -xe or vim /var/log/secure (if The storage location of the sshd logs has not been changed)
Thanks!
I am trying to setup x11vnc service on raspberry pi 4B platform, but it's failing. Below are the status logs:
root#raspberrypi4-64:~# systemctl status x11vnc.service
x x11vnc.service - x11vnc service
Loaded: loaded (/lib/systemd/system/x11vnc.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2022-11-23 09:44:49 UTC; 10s ago
Process: 1947 ExecStart=/usr/bin/x11vnc -forever -display :0 -auth guess -passwdfile /home/root/.vnc/passwd (code=exited, status=1/FAILURE)
Main PID: 1947 (code=exited, status=1/FAILURE)
Nov 23 09:44:49 raspberrypi4-64 systemd[1]: x11vnc.service: Failed with re...e'.
Nov 23 09:44:49 raspberrypi4-64 systemd[1]: x11vnc.service: Scheduled rest... 5.
Nov 23 09:44:49 raspberrypi4-64 systemd[1]: Stopped x11vnc service.
Nov 23 09:44:49 raspberrypi4-64 systemd[1]: x11vnc.service: Start request ...ly.
Nov 23 09:44:49 raspberrypi4-64 systemd[1]: x11vnc.service: Failed with re...e'.
Nov 23 09:44:49 raspberrypi4-64 systemd[1]: Failed to start x11vnc service.
Hint: Some lines were ellipsized, use -l to show in full.
Any suggestion on this will be really helpful.
I am expecting to enable x11vnc service on raspberry pi 4B.
ssh service is not getting started after upgrading debian 8 jessie to debian 9 strech
● ssh.service - OpenBSD Secure Shell server Loaded: loaded
(/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2021-05-28 13:36:30 UTC;
10min ago Process: 2155 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
(code=exited, status=255) Process: 2152 ExecStartPre=/usr/sbin/sshd
-t (code=exited, status=0/SUCCESS) Main PID: 2155 (code=exited, status=255)
May 28 13:36:29 ip-172-31-43-40 systemd[1]: Starting OpenBSD Secure
Shell server... May 28 13:36:30 ip-172-31-43-40 systemd[1]:
ssh.service: Main process exited, code=exited, status=255/n/a May 28
13:36:30 ip-172-31-43-40 systemd[1]: Failed to start OpenBSD Secure
Shell server. May 28 13:36:30 ip-172-31-43-40 systemd[1]: ssh.service:
Unit entered failed state. May 28 13:36:30 ip-172-31-43-40 systemd[1]:
ssh.service: Failed with result 'exit-code'.
kindly check the source list, in your source list might be something that disables the SSH
kindly use the different source list
Kindly change your /etc/apt/source.list to this Link it might work.
I am new to Linux and RPi. I want to transfer a file from my Pi to my PC.
With ...
scp hello pi#192.168.1.101:/home/pi
.. I am able to transfer my file "hell" to my Pi.
But when I try to send the file "elle" with ...
scp elle mirco#192.168.1.104:/home/mirco
i get
ssh: connect to host 192.168.1.104 port 22: Connection timed out lost connection
I read the ssh service status from the pi and my Computer:
Pi:
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; disabled; vendor preset: enabled)
Active: active (running) since Wed 2020-04-08 14:38:18 CEST; 6s ago
Docs: man:sshd(8)
man:sshd_config(5)
Process: 14004 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Main PID: 14006 (sshd)
Tasks: 1 (limit: 4915)
Memory: 804.0K
CGroup: /system.slice/ssh.service
└─14006 /usr/sbin/sshd -D
Apr 08 14:38:18 raspberrypi systemd[1]: Starting OpenBSD Secure Shell server...
Apr 08 14:38:18 raspberrypi sshd[14006]: Server listening on 0.0.0.0 port 22.
Apr 08 14:38:18 raspberrypi sshd[14006]: Server listening on :: port 22.
Apr 08 14:38:18 raspberrypi systemd[1]: Started OpenBSD Secure Shell server.
My Computer:
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-04-08 14:52:26 CEST; 6min ago
Process: 9224 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 9216 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Process: 8934 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Main PID: 8935 (sshd)
Tasks: 1 (limit: 4578)
CGroup: /system.slice/ssh.service
└─8935 /usr/sbin/sshd -D
Apr 08 14:52:26 ComputerMirco systemd[1]: Stopping OpenBSD Secure Shell server...
Apr 08 14:52:26 ComputerMirco systemd[1]: Stopped OpenBSD Secure Shell server.
Apr 08 14:52:26 ComputerMirco sshd[8935]: Server listening on 0.0.0.0 port 22.
Apr 08 14:52:26 ComputerMirco systemd[1]: Starting OpenBSD Secure Shell server...
Apr 08 14:52:26 ComputerMirco systemd[1]: Started OpenBSD Secure Shell server.
Apr 08 14:58:12 ComputerMirco systemd[1]: Reloading OpenBSD Secure Shell server.
Apr 08 14:58:12 ComputerMirco sshd[8935]: Received SIGHUP; restarting.
Apr 08 14:58:12 ComputerMirco sshd[8935]: Server listening on 0.0.0.0 port 22.
Can someone help me?
Thank you!
Mirco
Am I correct in thinking you're running the second SCP command on your Pi? If so, your Pi isn't authorized to connect to your PC. You can add it's public key to your authorized_keys file and your Pi will be able to connect to your PC.
You could also pull the file in from your Pi. This is safer because you don't really want your Pi to be able to connect to your PC.
SCP copy to host example
scp pi#192.168.1.101:/home/pi/elle /home/mirco
My guess is that your PC doesn't have ssh enabled.
Install openssh-server on your PC using
sudo apt install openssh-server
After installing this, a system service called ssh should have become active.
You can test this using
sudo systemctl status ssh
Your output should look something like this
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-04-08 10:05:07 IST; 13h ago
If it doesn't show active(running), try executing
sudo systemctl enable ssh
If you still are not able to ssh, enable the ssh port through your firewall.
In Ubuntu this can be done by
sudo ufw allow ssh
I am trying to install OpenIMSCore and following the steps from this link and I am getting the below error when trying to restart the network,
root#ubuntu16:~/.test/OpenIMSCore# /etc/init.d/networking restart
[....] Restarting networking (via systemctl): networking.serviceJob for networking.service failed because the control process exited with error code. See "systemctl status networking.service" and "journalctl -xe" for details.
failed!
root#ubuntu16:~/.test/OpenIMSCore# systemctl status networking.service
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
Active: failed (Result: exit-code) since Sat 2018-08-04 01:17:51 IST; 19s ago
Docs: man:interfaces(5)
Process: 27064 ExecStop=/sbin/ifdown -a --read-environment --exclude=lo (code=exited, status=1/FAILURE)
Process: 27167 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 27164 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=ex
Main PID: 27167 (code=exited, status=1/FAILURE)
Aug 04 01:17:51 ubuntu16 systemd[1]: Starting Raise network interfaces...
Aug 04 01:17:51 ubuntu16 sh[27164]: /etc/network/interfaces:4: option with empty value
Aug 04 01:17:51 ubuntu16 sh[27164]: ifquery: couldn't read interfaces file "/etc/network/interfaces"
Aug 04 01:17:51 ubuntu16 ifup[27167]: /etc/network/interfaces:4: option with empty value
Aug 04 01:17:51 ubuntu16 ifup[27167]: /sbin/ifup: couldn't read interfaces file "/etc/network/interfaces"
Aug 04 01:17:51 ubuntu16 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Aug 04 01:17:51 ubuntu16 systemd[1]: Failed to start Raise network interfaces.
Aug 04 01:17:51 ubuntu16 systemd[1]: networking.service: Unit entered failed state.
Aug 04 01:17:51 ubuntu16 systemd[1]: networking.service: Failed with result 'exit-code'.
After debugging I found that the issue was with the /etc/network/interfaces file, when added the below params (from DEVICE, HWADDR to PEERDNS) and start the network I am getting the above error.
Did anyone face the same issues while modifying the interfaces file (my /etc/hosts file & /etc/resolv.conf file are similar to the once provided in the above link).
Any reference on this would also be of great help !
Thanks in advance.
You'll probably kick yourself, but you've got the same typo on two lines. It should be iface eth0 inet dhcp not dchp.
ifup and ifdown will break if they can't parse the file.