-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting up and running / installation documentation #84
Comments
What do the logs say? |
How do I access the logs? |
If your Argus binary is located under You must also change the systemd service [Unit]
Description=Argus Server
Documentation=https://release-argus.io/docs
After=network-online.target
[Service]
User=argus
Restart=on-failure
ExecStart=/home/argus/argus/Argus-0.6.0.linux-amd64 \
-config.file=/home/argus/argus/config.yml
[Install]
WantedBy=multi-user.target To see the logs you can use |
Did you definitely start the systemd service? systemctl daemon-reload
systemctl start argus Logs - |
made the change @larsl-net suggested but still no luck... ran systemctl status argus service: @SARGUS argus]$ sudo systemctl status argus.service
● argus.service - Argus Server
Loaded: loaded (/etc/systemd/system/argus.service; enabled; vendor preset: disabled)
Active: failed (thawing) (Result: exit-code) since Wed 2022-06-08 10:07:03 EDT; 41s ago
Docs: https://release-argus.io/docs
Process: 2541 ExecStart=/home/argus/argus/Argus-0.6.0.linux-amd64 -config.file=/home/argus/argus/config.yml (code=exited, status=203/EXEC)
Main PID: 2541 (code=exited, status=203/EXEC)
Jun 08 10:07:02 SARGUS systemd[1]: argus.service: Failed with result 'exit-code'.
Jun 08 10:07:03 SARGUS systemd[1]: argus.service: Service RestartSec=100ms expired, scheduling restart.
Jun 08 10:07:03 SARGUS systemd[1]: argus.service: Scheduled restart job, restart counter is at 5.
Jun 08 10:07:03 SARGUS systemd[1]: Stopped Argus Server.
Jun 08 10:07:03 SARGUS systemd[1]: argus.service: Start request repeated too quickly.
Jun 08 10:07:03 SARGUS systemd[1]: argus.service: Failed with result 'exit-code'.
Jun 08 10:07:03 SARGUS systemd[1]: Failed to start Argus Server.
Jun 08 10:07:09 SARGUS systemd[1]: argus.service: Start request repeated too quickly.
Jun 08 10:07:09 SARGUS systemd[1]: argus.service: Failed with result 'exit-code'.
Jun 08 10:07:09 SARGUS systemd[1]: Failed to start Argus Server. and journalctl -u argus -- Logs begin at Wed 2022-06-08 09:59:00 EDT, end at Wed 2022-06-08 10:09:05 EDT. --
Jun 08 09:59:07 SARGUS systemd[1]: Started Argus Server.
Jun 08 09:59:07 SARGUS systemd[1]: argus.service: Main process exited, code=exited, status=203/EXEC
Jun 08 09:59:07 SARGUS systemd[1]: argus.service: Failed with result 'exit-code'.
Jun 08 09:59:08 SARGUS systemd[1]: argus.service: Service RestartSec=100ms expired, scheduling restart.
Jun 08 09:59:08 SARGUS systemd[1]: argus.service: Scheduled restart job, restart counter is at 1.
Jun 08 09:59:08 SARGUS systemd[1]: Stopped Argus Server.
... |
Easiest way to see if it's an issue with the config/perms, run /home/argus/argus/Argus-0.6.0.linux-amd64 -config.file=/home/argus/argus/config.yml |
@quantumzedno, checking your cert_file: '' # HTTPS Cert path, e.g. `cert.pem`
pkey_file: '' # HTTPS PrivKey path, e.g. `privkey.pem` are causing this issue. I'll do a commit to check that these files exist before trying to use them. I won't do another release just for this though. In the meantime, just comment out/remove these lines and it should work |
Running /home/argus/argus/Argus-0.6.0.linux-amd64 -config.file=/home/argus/argus/config.yml seems to work after making that change
however the service is still failing to run with the same error: -- Logs begin at Wed 2022-06-08 11:04:41 EDT, end at Wed 2022-06-08 11:08:36 EDT. --
Jun 08 11:05:37 SARGUS systemd[1]: Started Argus Server.
Jun 08 11:05:37 SARGUS systemd[1]: argus.service: Main process exited, code=exited, status=203/EXEC
Jun 08 11:05:37 SARGUS systemd[1]: argus.service: Failed with result 'exit-code'.
Jun 08 11:05:37 SARGUS systemd[1]: argus.service: Service RestartSec=100ms expired, scheduling restart.
Jun 08 11:05:37 SARGUS systemd[1]: argus.service: Scheduled restart job, restart counter is at 1.
Jun 08 11:05:37 SARGUS systemd[1]: Stopped Argus Server.
... |
Perm issues? |
worked fine: [lockwobe@SARGUS ~]$ sudo -u argus /home/argus/argus/Argus-0.6.0.linux-amd64 -config.file=/home/argus/argus/config.yml
|
SELinux? https://serverfault.com/a/1013293 |
also handles cert/key being and empty string #84 (comment)
also handles cert/key being an empty string (so use http) #84 (comment)
That did it! thank you so much for all the help, greatly appreciate it. |
Hi there,
I am very interested in this project and have been trying to set up a test vm with it for awhile but i've been struggling to get it up and running with the getting started documentation and was hoping to get some assistance/ request (or even help create) better setup documentation once I understand how to get going:
what i've done so far:
downloaded latest binary Argus-0.6.0.linux-amd64
transferred binary to centos 8 vm via scp
gave the binary execute permissions via chmod
ran ./Argus-0.6.0.linux-amd64 -help
created a /home/argus/argus directory structure and moved the binary to /home/argus/argus/Argus-0.6.0.linux-amd64
created a config.yml at /home/argus/argus/config.yml
created a systemd service file at /etc/systemd/system/argus.service
I'm not sure what else, but i feel like i'm definitely missing something....
i cant hit the web ui at the boxes ip address (172.29.2.128:8080)
also tried disabling firewall and se linux so it's neither of those
The text was updated successfully, but these errors were encountered: