You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been trying to figure out this error for several days, but I can't find the solution.
└─# service king-phisher start
Job for king-phisher.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status king-phisher.service" and "journalctl -xeu king-phisher.service" for details.
systemctl status king-phisher.service
× king-phisher.service - King Phisher Server
Loaded: loaded (/lib/systemd/system/king-phisher.service; enabled; preset: disabled)
Active: failed (Result: protocol) since Sun 2023-10-29 17:52:13 EDT; 6s ago
Process: 25338 ExecStart=/usr/bin/python3 /opt/king-phisher/KingPhisherServer /opt/king-phisher/server_config.yml (code=exited, status=0/SUCCESS)
CPU: 705ms
oct 29 17:52:12 kali systemd[1]: Starting king-phisher.service - King Phisher Server...
oct 29 17:52:13 kali python3[25338]: Loading .env environment variables...
oct 29 17:52:13 kali systemd[1]: king-phisher.service: Can't open PID file /run/king-phisher.pid (yet?) after start: No such file or directory
oct 29 17:52:13 kali systemd[1]: king-phisher.service: Failed with result 'protocol'.
oct 29 17:52:13 kali systemd[1]: Failed to start king-phisher.service - King Phisher Server.
└─# journalctl -xeu king-phisher.service
░░ A start job for unit king-phisher.service has finished with a failure.
░░
░░ The job identifier is 2611 and the job result is failed.
oct 29 17:45:15 kali systemd[1]: Starting king-phisher.service - King Phisher Server...
░░ Subject: A start job for unit king-phisher.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit king-phisher.service has begun execution.
░░
░░ The job identifier is 2681.
oct 29 17:45:16 kali python3[21124]: Loading .env environment variables...
oct 29 17:45:16 kali systemd[1]: king-phisher.service: Can't open PID file /run/king-phisher.pid (yet?) after start: No such file or directory
oct 29 17:45:16 kali systemd[1]: king-phisher.service: Failed with result 'protocol'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit king-phisher.service has entered the 'failed' state with result 'protocol'.
oct 29 17:45:16 kali systemd[1]: Failed to start king-phisher.service - King Phisher Server.
░░ Subject: A start job for unit king-phisher.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit king-phisher.service has finished with a failure.
░░
░░ The job identifier is 2681 and the job result is failed.
oct 29 17:52:12 kali systemd[1]: Starting king-phisher.service - King Phisher Server...
░░ Subject: A start job for unit king-phisher.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit king-phisher.service has begun execution.
░░
░░ The job identifier is 2751.
oct 29 17:52:13 kali python3[25338]: Loading .env environment variables...
oct 29 17:52:13 kali systemd[1]: king-phisher.service: Can't open PID file /run/king-phisher.pid (yet?) after start: No such file or directory
oct 29 17:52:13 kali systemd[1]: king-phisher.service: Failed with result 'protocol'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit king-phisher.service has entered the 'failed' state with result 'protocol'.
oct 29 17:52:13 kali systemd[1]: Failed to start king-phisher.service - King Phisher Server.
░░ Subject: A start job for unit king-phisher.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit king-phisher.service has finished with a failure.
░░
░░ The job identifier is 2751 and the job result is failed.
The truth is I'm super new to this and I understand it a lot, if someone could help me or guide me.
Thank you in advance for your support
The text was updated successfully, but these errors were encountered:
Hello, how are you, very good morning.
I have been trying to figure out this error for several days, but I can't find the solution.
└─# service king-phisher start
Job for king-phisher.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status king-phisher.service" and "journalctl -xeu king-phisher.service" for details.
systemctl status king-phisher.service
× king-phisher.service - King Phisher Server
Loaded: loaded (/lib/systemd/system/king-phisher.service; enabled; preset: disabled)
Active: failed (Result: protocol) since Sun 2023-10-29 17:52:13 EDT; 6s ago
Process: 25338 ExecStart=/usr/bin/python3 /opt/king-phisher/KingPhisherServer /opt/king-phisher/server_config.yml (code=exited, status=0/SUCCESS)
CPU: 705ms
oct 29 17:52:12 kali systemd[1]: Starting king-phisher.service - King Phisher Server...
oct 29 17:52:13 kali python3[25338]: Loading .env environment variables...
oct 29 17:52:13 kali systemd[1]: king-phisher.service: Can't open PID file /run/king-phisher.pid (yet?) after start: No such file or directory
oct 29 17:52:13 kali systemd[1]: king-phisher.service: Failed with result 'protocol'.
oct 29 17:52:13 kali systemd[1]: Failed to start king-phisher.service - King Phisher Server.
└─# journalctl -xeu king-phisher.service
░░ A start job for unit king-phisher.service has finished with a failure.
░░
░░ The job identifier is 2611 and the job result is failed.
oct 29 17:45:15 kali systemd[1]: Starting king-phisher.service - King Phisher Server...
░░ Subject: A start job for unit king-phisher.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit king-phisher.service has begun execution.
░░
░░ The job identifier is 2681.
oct 29 17:45:16 kali python3[21124]: Loading .env environment variables...
oct 29 17:45:16 kali systemd[1]: king-phisher.service: Can't open PID file /run/king-phisher.pid (yet?) after start: No such file or directory
oct 29 17:45:16 kali systemd[1]: king-phisher.service: Failed with result 'protocol'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit king-phisher.service has entered the 'failed' state with result 'protocol'.
oct 29 17:45:16 kali systemd[1]: Failed to start king-phisher.service - King Phisher Server.
░░ Subject: A start job for unit king-phisher.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit king-phisher.service has finished with a failure.
░░
░░ The job identifier is 2681 and the job result is failed.
oct 29 17:52:12 kali systemd[1]: Starting king-phisher.service - King Phisher Server...
░░ Subject: A start job for unit king-phisher.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit king-phisher.service has begun execution.
░░
░░ The job identifier is 2751.
oct 29 17:52:13 kali python3[25338]: Loading .env environment variables...
oct 29 17:52:13 kali systemd[1]: king-phisher.service: Can't open PID file /run/king-phisher.pid (yet?) after start: No such file or directory
oct 29 17:52:13 kali systemd[1]: king-phisher.service: Failed with result 'protocol'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit king-phisher.service has entered the 'failed' state with result 'protocol'.
oct 29 17:52:13 kali systemd[1]: Failed to start king-phisher.service - King Phisher Server.
░░ Subject: A start job for unit king-phisher.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit king-phisher.service has finished with a failure.
░░
░░ The job identifier is 2751 and the job result is failed.
The truth is I'm super new to this and I understand it a lot, if someone could help me or guide me.
Thank you in advance for your support
The text was updated successfully, but these errors were encountered: