I am a newbie in IPFS. I am trying to install and run the IPFS service in my Ubuntu server and hosting on the MS Azure VM instance.
Everything went well, except for one thing when I run the IPFS as service using systemd.
Here is the error that I caught it from the log file.
Aug 17 01:56:25 UbuntuTest systemd[1]: Started IPFS daemon.
Aug 17 01:56:25 UbuntuTest systemd[1]: ipfs.service: Main process exited, code=exited, status=217/USER
Aug 17 01:56:25 UbuntuTest systemd[1]: ipfs.service: Unit entered failed state.
Aug 17 01:56:25 UbuntuTest systemd[1]: ipfs.service: Failed with result 'exit-code'.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Service hold-off time over, scheduling restart.
Aug 17 01:56:26 UbuntuTest systemd[1]: Stopped IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: Started IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Main process exited, code=exited, status=217/USER
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Unit entered failed state.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Failed with result 'exit-code'.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Service hold-off time over, scheduling restart.
Aug 17 01:56:26 UbuntuTest systemd[1]: Stopped IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: Started IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Main process exited, code=exited, status=217/USER
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Unit entered failed state.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Failed with result 'exit-code'.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Service hold-off time over, scheduling restart.
Aug 17 01:56:26 UbuntuTest systemd[1]: Stopped IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: Started IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Main process exited, code=exited, status=217/USER
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Unit entered failed state.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Failed with result 'exit-code'.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Service hold-off time over, scheduling restart.
Aug 17 01:56:26 UbuntuTest systemd[1]: Stopped IPFS daemon.
Aug 17 01:56:26 UbuntuTest systemd[1]: ipfs.service: Start request repeated too quickly.
Aug 17 01:56:26 UbuntuTest systemd[1]: Failed to start IPFS daemon
.
The log file it seems no longer generate info.
Why does that happen?
When I run with ipfs daemon and it works well without error.
Please advise.
Thank you
Related
I added some files to systemed folder on my CentOS, after that postgresql service can not start with the error -
Job for postgresql-14.service failed because the control process exited with error code. See "systemctl status postgresql-14.service" and "journalctl -xe" for details.
systemctl status -
Feb 08 20:47:38 82-166-106-208.barak-online.net systemd[1]: Starting PostgreSQL 14 database server...
Feb 08 20:47:38 82-166-106-208.barak-online.net postmaster[2525]: 2023-02-08 20:47:38.805 IST [2525] LOG: redirecting log output to logging collector process
Feb 08 20:47:38 82-166-106-208.barak-online.net postmaster[2525]: 2023-02-08 20:47:38.805 IST [2525] HINT: Future log output will appear in directory "log".
Feb 08 20:47:38 82-166-106-208.barak-online.net systemd[1]: postgresql-14.service: main process exited, code=exited, status=1/FAILURE
Feb 08 20:47:38 82-166-106-208.barak-online.net systemd[1]: Failed to start PostgreSQL 14 database server.
Feb 08 20:47:38 82-166-106-208.barak-online.net systemd[1]: Unit postgresql-14.service entered failed state.
Feb 08 20:47:38 82-166-106-208.barak-online.net systemd[1]: postgresql-14.service failed.
journalctl -xe
-- Unit postgresql-14.service has begun starting up.
Feb 08 20:47:38 82-166-106-208.barak-online.net postmaster[2525]: 2023-02-08 20:47:38.805 IST [2525] LOG: redirecting log output to logging collector process
Feb 08 20:47:38 82-166-106-208.barak-online.net postmaster[2525]: 2023-02-08 20:47:38.805 IST [2525] HINT: Future log output will appear in directory "log".
Feb 08 20:47:38 82-166-106-208.barak-online.net systemd[1]: postgresql-14.service: main process exited, code=exited, status=1/FAILURE
Feb 08 20:47:38 82-166-106-208.barak-online.net systemd[1]: Failed to start PostgreSQL 14 database server.
-- Subject: Unit postgresql-14.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit postgresql-14.service has failed.
--
-- The result is failed.
Feb 08 20:47:38 82-166-106-208.barak-online.net systemd[1]: Unit postgresql-14.service entered failed state.
Feb 08 20:47:38 82-166-106-208.barak-online.net systemd[1]: postgresql-14.service failed.
Feb 08 20:47:38 82-166-106-208.barak-online.net polkitd[774]: Unregistered Authentication Agent for unix-process:2512:147782 (system bus name :1.40, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_IN
lines 2104-2163/2163 (END)
Appears to be an authentication error, check this out https://www.sqlshack.com/learn-postgresql-install-postgresql-on-centos-linux/
could someone help me with this error please:
Output for command: systemctl start postgresql-13.service
Job for postgresql-13.service failed because the control process exited with error code.
See "systemctl status postgresql-13.service" and "journalctl -xeu postgresql-13.service" for details.
Output for command systemctl status postgresql-13.service
× postgresql-13.service - PostgreSQL 13 database server
Loaded: loaded (/usr/lib/systemd/system/postgresql-13.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2022-08-23 12:17:50 CDT; 1min 47s ago
Docs: https://www.postgresql.org/docs/13/static/
Process: 1079 ExecStartPre=/usr/pgsql-13/bin/postgresql-13-check-db-dir ${PGDATA} (code=exited, status=0/SUCCESS)
Process: 1110 ExecStart=/usr/pgsql-13/bin/postmaster -D ${PGDATA} (code=exited, status=1/FAILURE)
Main PID: 1110 (code=exited, status=1/FAILURE)
CPU: 40ms
Aug 23 12:17:47 fedora systemd[1]: Starting PostgreSQL 13 database server...
Aug 23 12:17:50 fedora postmaster[1110]: 2022-08-23 12:17:50.144 CDT [1110] LOG: redirecting log output to logging collector process
Aug 23 12:17:50 fedora postmaster[1110]: 2022-08-23 12:17:50.144 CDT [1110] HINT: Future log output will appear in directory "log".
Aug 23 12:17:50 fedora systemd[1]: postgresql-13.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 12:17:50 fedora systemd[1]: postgresql-13.service: Killing process 1132 (postmaster) with signal SIGKILL.
Aug 23 12:17:50 fedora systemd[1]: postgresql-13.service: Killing process 1132 (postmaster) with signal SIGKILL.
Aug 23 12:17:50 fedora systemd[1]: postgresql-13.service: Failed with result 'exit-code'.
Aug 23 12:17:50 fedora systemd[1]: postgresql-13.service: Unit process 1132 (postmaster) remains running after unit stopped.
Aug 23 12:17:50 fedora systemd[1]: Failed to start PostgreSQL 13 database server.
Already I uninstall and reinstall postgresql but nothing works. Also I tried to install postgresql-14 but I get the same error.
I have to install postgresql to work alongs with Ruby on Rails.
I have an issue where MongoDB keeps crashing on me:
$ sudo cat /var/log/syslog ->
Nov 28 14:06:58 ns557017 systemd[1]: mongod.service: Main process exited, code=killed, status=6/ABRT
Nov 28 14:06:58 ns557017 systemd[1]: mongod.service: Unit entered failed state.
Nov 28 14:06:58 ns557017 systemd[1]: mongod.service: Failed with result 'signal'.
Nov 28 14:06:59 ns557017 systemd[1]: mongod.service: Service hold-off time over, scheduling restart.
Nov 28 14:06:59 ns557017 systemd[1]: Stopped MongoDB Database Server.
I am using Mongo's free monitoring, and it points me towards the CPU being overused:
However if I look at htop, the CPU always seems fine:
How can I deduce what is causing Mongo to crash on me? Thanks
Following https://www.vultr.com/docs/how-to-install-sonarqube-on-centos-7 to install SonarQube on my CentOS.
When I'm trying to start the SonarQube via sudo systemctl start sonar it is giving below error:
Job for sonar.service failed because the control process exited with error code. See "systemctl status sonar.service" and "journalctl -xe" for details.
Output of systemctl status sonar.service:
sonar.service - SonarQube service
Loaded: loaded (/etc/systemd/system/sonar.service; disabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Wed 2019-04-24 16:56:39 UTC; 19s ago
Process: 23573 ExecStart=/opt/sonarqube/bin/linux-x86-64/sonar.sh start (code=exited, status=203/EXEC)
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: sonar.service: control process exited, code=exited status=203
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: Failed to start SonarQube service.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: Unit sonar.service entered failed state.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: sonar.service failed.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: sonar.service holdoff time over, scheduling restart.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: start request repeated too quickly for sonar.service
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: Failed to start SonarQube service.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: Unit sonar.service entered failed state.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: sonar.service failed.
Output of journalctl -xe:
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: Starting SonarQube service...
-- Subject: Unit sonar.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sonar.service has begun starting up.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[23573]: Failed at step EXEC spawning /opt/sonarqube/bin/linux-x86-64/sona
-- Subject: Process /opt/sonarqube/bin/linux-x86-64/sonar.sh could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /opt/sonarqube/bin/linux-x86-64/sonar.sh could not be executed and failed.
--
-- The error number returned by this process is 2.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: sonar.service: control process exited, code=exited status=203
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: Failed to start SonarQube service.
-- Subject: Unit sonar.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sonar.service has failed.
--
-- The result is failed.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: Unit sonar.service entered failed state.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: sonar.service failed.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: sonar.service holdoff time over, scheduling restart.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: start request repeated too quickly for sonar.service
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: Failed to start SonarQube service.
-- Subject: Unit sonar.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sonar.service has failed.
--
-- The result is failed.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: Unit sonar.service entered failed state.
Apr 24 16:56:39 ip-172-31-13-96.ap-south-1.compute.internal systemd[1]: sonar.service failed.
status=203/EXEC means that systemd cannot execute ExecStart script. The most "popular" reasons are:
incorrect path to script
script has invalid permissions:
service user does not have permission to read script
script is not marked as executable
I hope /opt/sonarqube/bin/linux-x86-64/sonar.sh exists, so please verify that the script is marked as executable.
I'm trying to install Plex media server on my raspberrypi zero w and i keep getting this error:
plexmediaserver.service - Plex Media Server for Linux
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-09-06 18:22:09 UTC; 12s ago
Process: 1043 ExecStart=/bin/sh -c LD_LIBRARY_PATH=/usr/lib/plexmediaserver "/usr/lib/plexmediaserv
Process: 1039 ExecStartPre=/bin/sh -c /usr/bin/test -d "${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR
Main PID: 1043 (code=exited, status=132)
Sep 06 18:22:04 raspberrypi systemd[1]: plexmediaserver.service: Unit entered failed state.
Sep 06 18:22:04 raspberrypi systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
Sep 06 18:22:09 raspberrypi systemd[1]: plexmediaserver.service: Service hold-off time over, scheduli
Sep 06 18:22:09 raspberrypi systemd[1]: Stopped Plex Media Server for Linux.
Sep 06 18:22:09 raspberrypi systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Sep 06 18:22:09 raspberrypi systemd[1]: Failed to start Plex Media Server for Linux.
Sep 06 18:22:09 raspberrypi systemd[1]: plexmediaserver.service: Unit entered failed state.
Sep 06 18:22:09 raspberrypi systemd[1]: plexmediaserver.service: Failed with result 'exit-code'.
If anyone can help I'd really appreciate it, Thanks!
(btw I'm quite a noob when it comes to raspberry pi's)
As far as I know it is not supported anymore due to lots of API changes of Plex resulting in the discontinued support of ARM v61 (Pi Zero W has ARM v61) and only "supports" ARM v7 and v8 (v64)
See also: https://forums.plex.tv/t/pi-zero-w-problems/191899/7