I'm trying to install ssl certificate on aws ec2(Amazon Linux2). Apache can start properly until I configure ssl following "Step 1: Enable TLS on the server" in https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/SSL-on-amazon-linux-ami.html
After I make those changes, apache even can not start:
Job for httpd.service failed because the control process exited with error code
I got the following log by typing "journalctl -xe":
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-26.scope has begun starting up.
Jan 27 04:30:01 ip-172-31-18-58.ap-southeast-2.compute.internal CROND[10239]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jan 27 04:30:01 ip-172-31-18-58.ap-southeast-2.compute.internal systemd[1]: Removed slice User Slice of root.
-- Subject: Unit user-0.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has finished shutting down.
Jan 27 04:30:01 ip-172-31-18-58.ap-southeast-2.compute.internal systemd[1]: Stopping User Slice of root.
-- Subject: Unit user-0.slice has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has begun shutting down.
Jan 27 04:30:47 ip-172-31-18-58.ap-southeast-2.compute.internal sshd[10245]: Received disconnect from 221.181.185.135 port 21146:11: [preauth]
Jan 27 04:30:47 ip-172-31-18-58.ap-southeast-2.compute.internal sshd[10245]: Disconnected from 221.181.185.135 port 21146 [preauth]
Jan 27 04:31:22 ip-172-31-18-58.ap-southeast-2.compute.internal dhclient[2893]: XMT: Solicit on eth0, interval 120170ms.
Jan 27 04:33:22 ip-172-31-18-58.ap-southeast-2.compute.internal dhclient[2893]: XMT: Solicit on eth0, interval 119290ms.
Jan 27 04:34:55 ip-172-31-18-58.ap-southeast-2.compute.internal sshd[10251]: Received disconnect from 218.93.208.150 port 29589:11: [preauth]
Jan 27 04:34:55 ip-172-31-18-58.ap-southeast-2.compute.internal sshd[10251]: Disconnected from 218.93.208.150 port 29589 [preauth]
Jan 27 04:35:17 ip-172-31-18-58.ap-southeast-2.compute.internal sudo[10253]: ec2-user : TTY=pts/2 ; PWD=/etc/pki/tls/certs ; USER=root ; COMMAND=/bin/systemct
Jan 27 04:35:17 ip-172-31-18-58.ap-southeast-2.compute.internal sudo[10253]: pam_unix(sudo:session): session opened for user root by ec2-user(uid=0)
Jan 27 04:35:17 ip-172-31-18-58.ap-southeast-2.compute.internal systemd[1]: Starting The Apache HTTP Server...
-- Subject: Unit httpd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has begun starting up.
Jan 27 04:35:17 ip-172-31-18-58.ap-southeast-2.compute.internal systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Jan 27 04:35:17 ip-172-31-18-58.ap-southeast-2.compute.internal systemd[1]: Failed to start The Apache HTTP Server.
-- Subject: Unit httpd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit httpd.service has failed.
--
-- The result is failed.
Jan 27 04:35:17 ip-172-31-18-58.ap-southeast-2.compute.internal systemd[1]: Unit httpd.service entered failed state.
Jan 27 04:35:17 ip-172-31-18-58.ap-southeast-2.compute.internal systemd[1]: httpd.service failed.
Jan 27 04:35:17 ip-172-31-18-58.ap-southeast-2.compute.internal sudo[10253]: pam_unix(sudo:session): session closed for user root
Jan 27 04:35:22 ip-172-31-18-58.ap-southeast-2.compute.internal dhclient[2893]: XMT: Solicit on eth0, interval 130780ms.
I get stuck here for a long time. Anyone can help me please? Thank you in advance.
Related
I am unable to open Mosquitto beacause I have reached the start/restart limit over a certain period of time:
$ systemctl status mosquitto.service
● mosquitto.service - Mosquitto MQTT v3.1/v3.1.1 Broker
Loaded: loaded (/usr/lib/systemd/system/mosquitto.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/mosquitto.service.d
└─override.conf
Active: failed (Result: start-limit) since Fri 2023-02-03 21:45:41 UTC; 2h 12min ago
Docs: man:mosquitto.conf(5)
man:mosquitto(8)
Main PID: 543 (code=exited, status=1/FAILURE)
Feb 03 21:45:26 ip-172-31-11-142.us-west-1.compute.internal systemd[1]: mosquitto.service: main process exited, ...RE
Feb 03 21:45:26 ip-172-31-11-142.us-west-1.compute.internal systemd[1]: Failed to start Mosquitto MQTT v3.1/v3.1...r.
Feb 03 21:45:26 ip-172-31-11-142.us-west-1.compute.internal systemd[1]: Unit mosquitto.service entered failed state.
Feb 03 21:45:26 ip-172-31-11-142.us-west-1.compute.internal systemd[1]: mosquitto.service failed.
Feb 03 21:45:41 ip-172-31-11-142.us-west-1.compute.internal systemd[1]: mosquitto.service holdoff time over, sch...t.
Feb 03 21:45:41 ip-172-31-11-142.us-west-1.compute.internal systemd[1]: Stopped Mosquitto MQTT v3.1/v3.1.1 Broker.
Feb 03 21:45:41 ip-172-31-11-142.us-west-1.compute.internal systemd[1]: start request repeated too quickly for m...ce
Feb 03 21:45:41 ip-172-31-11-142.us-west-1.compute.internal systemd[1]: Failed to start Mosquitto MQTT v3.1/v3.1...r.
Feb 03 21:45:41 ip-172-31-11-142.us-west-1.compute.internal systemd[1]: Unit mosquitto.service entered failed state.
Feb 03 21:45:41 ip-172-31-11-142.us-west-1.compute.internal systemd[1]: mosquitto.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
I have the method of:
ps -ef | grep mosquito
sudo kill ####
and it still does not work
I have also attempted to do:
systemctl edit /etc/mosquitto
[Service]
Restart=always
RestartSec=15
StartLimitInterval=150
StartLimitBurst=8
I tried to install and start the Tomcat on my AWS EC2 instance.
However, I failed to run tomcat server after installed it.
I followed the following article for that
https://blog.devops4me.com/aws-tutorial-how-to-install-tomcat-in-aws-ec2-install/
And after finished step 6, and reloaded tomcat server, I tried to restart tomcat service like step 7. However, my terminal showed as below:
Feb 14 20:17:07 ip-172-31-54-104.ec2.internal systemd[1]: tomcat.service: control process exited, code=exited status=203
Feb 14 20:17:07 ip-172-31-54-104.ec2.internal systemd[1]: Failed to start Tomcat Server.
Feb 14 20:17:07 ip-172-31-54-104.ec2.internal systemd[1]: Unit tomcat.service entered failed state.
Feb 14 20:17:07 ip-172-31-54-104.ec2.internal systemd[1]: tomcat.service failed.
Feb 14 20:17:10 ip-172-31-54-104.ec2.internal systemd[1]: [/etc/systemd/system/tomcat.service:22] Missing '='.
Feb 14 20:17:22 ip-172-31-54-104.ec2.internal systemd[1]: tomcat.service holdoff time over, scheduling restart.
Feb 14 20:17:22 ip-172-31-54-104.ec2.internal systemd[1]: tomcat.service failed to schedule restart job: Unit is not loaded properly: Bad message.
Feb 14 20:17:22 ip-172-31-54-104.ec2.internal systemd[1]: Unit tomcat.service entered failed state.
Feb 14 20:17:22 ip-172-31-54-104.ec2.internal systemd[1]: tomcat.service failed.
I don't really understand how this work, and tried to search error on internet, but still doesn't have any clue of how to solve this problem, if anyone can give me a hint, that would be great, thank you!
I have Jenkins installed in an EC2 machine in AWS. I tried to install the slack plugin and it break the other plugins, so I tried updating Jenkins version to make it work again and now I cannot event start it. I get the following message:
Starting jenkins (via systemctl): Failed to start jenkins.service: Unit is not loaded properly: Invalid argument.
See system logs and 'systemctl status jenkins.service' for details.
[FAILED]
I have also tried to delete Jenkins completely following this guide: to then reinstall it following the Jenkins in AWS guide. But it is still not working. At some point when I did the journalctl -xe I got this error (I cant remember what I did to get there but at least I saved this log trace):
Unit jenkins.service has begun starting up.
Sep 20 16:39:49 ip-10-10-3-149.ec2.internal jenkins[23035]: Sep 20, 2022 4:39:49 PM executable.Main verifyJavaVersion
Sep 20 16:39:49 ip-10-10-3-149.ec2.internal jenkins[23035]: SEVERE: Running with Java class version 52, which is older than
Sep 20 16:39:49 ip-10-10-3-149.ec2.internal jenkins[23035]: java.lang.UnsupportedClassVersionError: 52.0
Sep 20 16:39:49 ip-10-10-3-149.ec2.internal jenkins[23035]: at executable.Main.verifyJavaVersion(Main.java:145)
Sep 20 16:39:49 ip-10-10-3-149.ec2.internal jenkins[23035]: at executable.Main.main(Main.java:109)
Sep 20 16:39:49 ip-10-10-3-149.ec2.internal jenkins[23035]: Jenkins requires Java versions [17, 11] but you are running wit
Sep 20 16:39:49 ip-10-10-3-149.ec2.internal jenkins[23035]: java.lang.UnsupportedClassVersionError: 52.0
Sep 20 16:39:49 ip-10-10-3-149.ec2.internal jenkins[23035]: at executable.Main.verifyJavaVersion(Main.java:145)
Sep 20 16:39:49 ip-10-10-3-149.ec2.internal jenkins[23035]: at executable.Main.main(Main.java:109)
Sep 20 16:39:49 ip-10-10-3-149.ec2.internal systemd[1]: Failed to start Jenkins Continuous Integration Server.
-- Subject: Unit jenkins.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit jenkins.service has failed.
--
So I though I had finally found the error, I checked the java -version and it was saying java1.8. Therefore I changed it with alternatives --config java and set it to:
java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.16.0.8-1.amzn2.0.1.x86_64/bin/java)
I have also added this path to /etc/rc.d/init.d/jenkins. Now when I get the java -version I get this:
openjdk version "11.0.16" 2022-07-19 LTS
OpenJDK Runtime Environment (Red_Hat-11.0.16.0.8-1.amzn2.0.1) (build 11.0.16+8-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-11.0.16.0.8-1.amzn2.0.1) (build 11.0.16+8-LTS, mixed mode, sharing)
when I try to get the status of jenkins with systemctl status jenkins.service -l I get:
● jenkins.service
Loaded: error (Reason: Invalid argument)
Drop-In: /etc/systemd/system/jenkins.service.d
└─override.conf
Active: failed (Result: start-limit) since Tue 2022-09-20 16:39:49 UTC; 15h ago
Main PID: 23035 (code=exited, status=0/SUCCESS)
Sep 20 16:57:30 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecStop= setting. Refusing.
Sep 20 16:57:43 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecStop= setting. Refusing.
Sep 21 07:15:59 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecStop= setting. Refusing.
Sep 21 07:20:02 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecStop= setting. Refusing.
Sep 21 07:23:12 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecStop= setting. Refusing.
Sep 21 07:23:20 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecStop= setting. Refusing.
Sep 21 07:24:26 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecStop= setting. Refusing.
Sep 21 07:30:58 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecStop= setting. Refusing.
Sep 21 07:31:06 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecStop= setting. Refusing.
Sep 21 07:48:04 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecStop= setting. Refusing.
and when I use journalctl -xe I get:
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-120.scope has finished starting up.
--
-- The start-up result is done.
Sep 21 07:40:01 ip-10-10-3-149.ec2.internal CROND[842]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Sep 21 07:41:28 ip-10-10-3-149.ec2.internal dhclient[3121]: XMT: Solicit on eth0, interval 131610ms.
Sep 21 07:43:39 ip-10-10-3-149.ec2.internal dhclient[3121]: XMT: Solicit on eth0, interval 118630ms.
Sep 21 07:45:38 ip-10-10-3-149.ec2.internal dhclient[3121]: XMT: Solicit on eth0, interval 121300ms.
Sep 21 07:46:59 ip-10-10-3-149.ec2.internal sshd[3483]: Received disconnect from 92.255.85.69 port 28784:
Sep 21 07:46:59 ip-10-10-3-149.ec2.internal sshd[3483]: Disconnected from 92.255.85.69 port 28784 [preaut
Sep 21 07:47:04 ip-10-10-3-149.ec2.internal dhclient[3075]: DHCPREQUEST on eth0 to 10.10.3.1 port 67 (xid
Sep 21 07:47:04 ip-10-10-3-149.ec2.internal dhclient[3075]: DHCPACK from 10.10.3.1 (xid=0x18dc5aad)
Sep 21 07:47:04 ip-10-10-3-149.ec2.internal NET[3542]: dhclient: Locked /run/dhclient/resolv.lock
Sep 21 07:47:04 ip-10-10-3-149.ec2.internal dhclient[3075]: bound to 10.10.3.149 -- renewal in 1618 secon
Sep 21 07:47:04 ip-10-10-3-149.ec2.internal ec2net[3561]: [get_meta] Querying IMDS for meta-data/network/
Sep 21 07:47:04 ip-10-10-3-149.ec2.internal ec2net[3562]: [get_meta] Getting token for IMDSv2.
Sep 21 07:47:04 ip-10-10-3-149.ec2.internal ec2net[3565]: [get_meta] Trying to get http://169.254.169.254
Sep 21 07:47:04 ip-10-10-3-149.ec2.internal ec2net[3570]: [remove_aliases] Removing aliases of eth0
Sep 21 07:47:39 ip-10-10-3-149.ec2.internal dhclient[3121]: XMT: Solicit on eth0, interval 116180ms.
Sep 21 07:48:03 ip-10-10-3-149.ec2.internal sudo[3947]: root : TTY=pts/0 ; PWD=/root ; USER=root ; CO
Sep 21 07:48:03 ip-10-10-3-149.ec2.internal sudo[3947]: pam_unix(sudo:session): session opened for user r
Sep 21 07:48:03 ip-10-10-3-149.ec2.internal systemd[1]: Reloading.
Sep 21 07:48:04 ip-10-10-3-149.ec2.internal systemd[1]: jenkins.service lacks both ExecStart= and ExecSto
Sep 21 07:48:04 ip-10-10-3-149.ec2.internal sudo[3947]: pam_unix(sudo:session): session closed for user r
Sep 21 07:48:09 ip-10-10-3-149.ec2.internal sudo[4019]: root : TTY=pts/0 ; PWD=/root ; USER=root ; CO
Sep 21 07:48:09 ip-10-10-3-149.ec2.internal sudo[4019]: pam_unix(sudo:session): session opened for user r
Sep 21 07:48:09 ip-10-10-3-149.ec2.internal sudo[4019]: pam_unix(sudo:session): session closed for user r
I have tried also the solution in here. I am not sure what else I can try.
UPDATE: this is how my jenkins unit looks like (systemctl cat jenkins):
# /etc/systemd/system/jenkins.service
[Service]
Environment="JENKINS_PORT=8000"
# /etc/systemd/system/jenkins.service.d/override.conf
[Service]
Environment="JENKINS_PORT=8000"
According to the logs, the unit file is missing start and stop scripts which can be confirmed by
systemctl cat jenkins.
According to Jenkins docs, the systemd file needed changes.Copying and overriding the unit file with the one given in the docs can solve the problem.
I am using centos 7.
How did I check the log.
journalctl -xe
What I got from the log.(I saw the same log every 10 seconds.)
Oct 02 10:19:51 lp01.localdomain systemd[1]: zabbix-agent.service holdoff time over, scheduling restart.
Oct 02 10:19:51 lp01.localdomain systemd[1]: Starting Zabbix Agent...
-- Subject: Unit zabbix-agent.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit zabbix-agent.service has begun starting up.
Oct 02 10:19:51 lp01.localdomain zabbix_agentd[8985]: zabbix_agentd [8987]: cannot open "/var/log/zabbix/zabbix_agentd.log": [13] Permission denied
Oct 02 10:19:51 lp01.localdomain systemd[1]: PID file /run/zabbix/zabbix_agentd.pid not readable (yet?) after start.
Oct 02 10:19:51 lp01.localdomain systemd[1]: zabbix-agent.service never wrote its PID file. Failing.
Oct 02 10:19:51 lp01.localdomain systemd[1]: Failed to start Zabbix Agent.
-- Subject: Unit zabbix-agent.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit zabbix-agent.service has failed.
--
-- The result is failed.
Oct 02 10:19:51 lp01.localdomain systemd[1]: Unit zabbix-agent.service entered failed state.
Oct 02 10:19:51 lp01.localdomain systemd[1]: zabbix-agent.service failed.
So I checked "/var/log/zabbix/zabbix_agentd.log" file first.
ll /var/log/zabbix/zabbix_agentd.log
But it said No such file or directory.
ls: cannot access /var/log/zabbix/zabbix_agentd.log: No such file or directory
and then I checked "/run/zabbix/zabbix_agentd.pid" file.
ll /run/zabbix/zabbix_agentd.pid
It also said No such file or directory.
ls: cannot access /run/zabbix/zabbix_agentd.pid: No such file or directory
You have new mail in /var/spool/mail/root
I checked if Selinux is running.
getenforce
and it said Selinux is Disabled..
My questions are
How can I start zabbix?
If I can't start zabbix, can I stop zabbix from starting-failing every 10 seconds?
Thank you.
add permission to the directory - /var/log/zabbix/ & /var/log/zabbix-agent/
chmod 707 /var/log/zabbix/
chmod 707 /var/log/zabbix-agent/
or
change owner of the directory?
chown zabbix:zabbix /var/log/zabbix/
chown zabbix:zabbix /var/log/zabbix-agent/
And then, would stop service zabbix?
systemctl stop zabbix-agent
My server has been working great for about 18 months. My setup is Nginx, Gunicorn, Django on a Ubuntu server. I will share this next piece of information just for the sake of full disclosure. One of my hard drives died on this same server. It's not the hard drive with any of the data that I'm referring to, but this hard disk did end up getting a new uuid. I feel compelled to share this information because this was when I started having trouble. Could be coincidence, could be related, I dunno. This was last Friday and I've been struggling with it ever since.
I get a 502 error. When I drill down a little bit that shows up as a Gunicorn error. I'll attach all of the information that I can think of below about my setup. But what gets me is that I can start Gunicorn from the command line, but not from the computer boot.
This works from the command line, which tells me that I have something right:
sudo service gunicorn stop
sudo /media/Storage/sales_portal/venv/bin/gunicorn --chdir=/media/Storage/sales_portal --timeout 600 --access-logfile /var/log/gunicorn/access.log --error-logfile /var/log/gunicorn/error.log --log-level debug --workers 3 --bind unix:/run/gunicorn.sock sales_portal.wsgi:application
My gunicorn.service file is:
[Unit]
Description=gunicorn daemon
Requires=gunicorn.socket
After=network.target
[Service]
# Type=notify
# the specific user that our service will run as
User=administrator
Group=administrator
# another option for an even more restricted service is
# DynamicUser=yes
# see http://0pointer.net/blog/dynamic-users-with-systemd.html
# RuntimeDirectory=gunicorn
WorkingDirectory=/media/Storage/sales_portal
ExecStart=/media/Storage/sales_portal/venv/bin/gunicorn --chdir=/media/Storage/sales_portal --timeout 600 --access-logfile /var/log/gunicorn/gunicorn.log --error-logfile /var/log/gunicorn/error.log --workers 3 --bind unix:/run/gunicorn.sock sales_portal.wsgi:application
# ExecReload=/bin/kill -s HUP $MAINPID
# KillMode=mixed
# TimeoutStopSec=5
# PrivateTmp=true
[Install]
WantedBy=multi-user.target
my gunicorn.socket information is:
[Unit]
Description=gunicorn socket
[Socket]
ListenStream=/run/gunicorn.sock
# Our service won't need permissions for the socket, since it
# inherits the file descriptor by socket activation
# only the nginx daemon will need access to the socket
# SocketUser=www-data
# Optionally restrict the socket permissions even more.
# SocketMode=600
[Install]
WantedBy=sockets.target
Trying
sudo service gunicorn start
gives me
A dependency job for gunicorn.service failed. See 'journalctl -xe' for details.
the output of this (or a portion of it, anyway) is:
Nov 20 08:21:11 server systemd[1172]: tracker-miner-fs.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Nov 20 08:21:11 server systemd[1172]: Failed to start Tracker file system data miner.
-- Subject: A start job for unit UNIT has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has finished with a failure.
--
-- The job identifier is 2343 and the job result is failed.
Nov 20 08:21:11 server systemd[1172]: tracker-store.service: Scheduled restart job, restart counter is at 1.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit UNIT has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Nov 20 08:21:11 server systemd[1172]: tracker-miner-fs.service: Scheduled restart job, restart counter is at 54.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit UNIT has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Nov 20 08:21:11 server systemd[1172]: Stopped Tracker file system data miner.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit UNIT has finished.
--
-- The job identifier is 2388 and the job result is done.
Nov 20 08:21:11 server systemd[1172]: Starting Tracker file system data miner...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has begun execution.
--
-- The job identifier is 2388.
Nov 20 08:21:11 server systemd[1172]: Stopped Tracker metadata database store and lookup manager.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit UNIT has finished.
--
-- The job identifier is 2373 and the job result is done.
Nov 20 08:21:11 server systemd[1172]: Starting Tracker metadata database store and lookup manager...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has begun execution.
--
-- The job identifier is 2373.
Nov 20 08:21:11 server tracker-miner-f[167517]: Set scheduler policy to SCHED_IDLE
Nov 20 08:21:11 server tracker-miner-f[167517]: Setting priority nice level to 19
Nov 20 08:21:11 server systemd[1172]: Started Tracker metadata database store and lookup manager.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 2373.
Nov 20 08:21:11 server tracker-miner-f[167517]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167517]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167517]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167517]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167517]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167517]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167517]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167517]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167517]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location.
Nov 20 08:21:11 server unknown[167518]: Cannot initialize database: tracker data directory does not exist and could not be created: Permission denied
Nov 20 08:21:11 server systemd[1172]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit UNIT has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Nov 20 08:21:11 server systemd[1172]: tracker-store.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Nov 20 08:21:11 server dbus-daemon[1215]: [session uid=1000 pid=1215] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.114' (uid=1000 pid=167517 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Nov 20 08:21:11 server systemd[1172]: tracker-store.service: Scheduled restart job, restart counter is at 2.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit UNIT has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Nov 20 08:21:11 server systemd[1172]: Stopped Tracker metadata database store and lookup manager.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit UNIT has finished.
--
-- The job identifier is 2403 and the job result is done.
Nov 20 08:21:11 server systemd[1172]: Starting Tracker metadata database store and lookup manager...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has begun execution.
--
-- The job identifier is 2403.
Nov 20 08:21:11 server dbus-daemon[1215]: [session uid=1000 pid=1215] Successfully activated service 'org.freedesktop.Tracker1'
Nov 20 08:21:11 server systemd[1172]: Started Tracker metadata database store and lookup manager.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 2403.
Nov 20 08:21:11 server tracker-store[167527]: Cannot initialize database: tracker data directory does not exist and could not be created: Permission denied
Nov 20 08:21:11 server systemd[1172]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit UNIT has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Nov 20 08:21:11 server systemd[1172]: tracker-store.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Nov 20 08:21:11 server tracker-miner-f[167517]: Couldn't create new Files miner: 'Failed to load SPARQL backend: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying'
Nov 20 08:21:11 server systemd[1172]: tracker-miner-fs.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit UNIT has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Nov 20 08:21:11 server systemd[1172]: tracker-miner-fs.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Nov 20 08:21:11 server systemd[1172]: Failed to start Tracker file system data miner.
-- Subject: A start job for unit UNIT has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has finished with a failure.
--
-- The job identifier is 2388 and the job result is failed.
Nov 20 08:21:11 server systemd[1172]: tracker-store.service: Scheduled restart job, restart counter is at 3.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit UNIT has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Nov 20 08:21:11 server systemd[1172]: tracker-miner-fs.service: Scheduled restart job, restart counter is at 55.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit UNIT has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Nov 20 08:21:11 server systemd[1172]: Stopped Tracker file system data miner.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit UNIT has finished.
--
-- The job identifier is 2448 and the job result is done.
Nov 20 08:21:11 server systemd[1172]: Starting Tracker file system data miner...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has begun execution.
--
-- The job identifier is 2448.
Nov 20 08:21:11 server systemd[1172]: Stopped Tracker metadata database store and lookup manager.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit UNIT has finished.
--
-- The job identifier is 2433 and the job result is done.
Nov 20 08:21:11 server systemd[1172]: Starting Tracker metadata database store and lookup manager...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has begun execution.
--
-- The job identifier is 2433.
Nov 20 08:21:11 server tracker-miner-f[167532]: Set scheduler policy to SCHED_IDLE
Nov 20 08:21:11 server tracker-miner-f[167532]: Setting priority nice level to 19
Nov 20 08:21:11 server systemd[1172]: Started Tracker metadata database store and lookup manager.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 2433.
Nov 20 08:21:11 server tracker-miner-f[167532]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167532]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167532]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location.
Nov 20 08:21:11 server tracker-store[167533]: Cannot initialize database: tracker data directory does not exist and could not be created: Permission denied
Nov 20 08:21:11 server tracker-miner-f[167532]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167532]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167532]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location.
Nov 20 08:21:11 server systemd[1172]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit UNIT has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Nov 20 08:21:11 server tracker-miner-f[167532]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167532]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location.
Nov 20 08:21:11 server tracker-miner-f[167532]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location.
Nov 20 08:21:11 server systemd[1172]: tracker-store.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Nov 20 08:21:11 server dbus-daemon[1215]: [session uid=1000 pid=1215] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.117' (uid=1000 pid=167532 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Nov 20 08:21:12 server systemd[1172]: tracker-store.service: Scheduled restart job, restart counter is at 4.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit UNIT has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Nov 20 08:21:12 server systemd[1172]: Stopped Tracker metadata database store and lookup manager.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit UNIT has finished.
--
-- The job identifier is 2463 and the job result is done.
Nov 20 08:21:12 server systemd[1172]: Starting Tracker metadata database store and lookup manager...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has begun execution.
--
-- The job identifier is 2463.
Nov 20 08:21:12 server dbus-daemon[1215]: [session uid=1000 pid=1215] Successfully activated service 'org.freedesktop.Tracker1'
Nov 20 08:21:12 server systemd[1172]: Started Tracker metadata database store and lookup manager.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 2463.
Nov 20 08:21:12 server tracker-store[167542]: Cannot initialize database: tracker data directory does not exist and could not be created: Permission denied
Nov 20 08:21:12 server systemd[1172]: tracker-store.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit UNIT has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Nov 20 08:21:12 server systemd[1172]: tracker-store.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Nov 20 08:21:12 server tracker-miner-f[167532]: Couldn't create new Files miner: 'Failed to load SPARQL backend: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying'
Nov 20 08:21:12 server systemd[1172]: tracker-miner-fs.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit UNIT has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Nov 20 08:21:12 server systemd[1172]: tracker-miner-fs.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Nov 20 08:21:12 server systemd[1172]: Failed to start Tracker file system data miner.
-- Subject: A start job for unit UNIT has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has finished with a failure.
--
-- The job identifier is 2448 and the job result is failed.
Nov 20 08:21:12 server systemd[1172]: tracker-store.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit UNIT has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Nov 20 08:21:12 server systemd[1172]: tracker-miner-fs.service: Scheduled restart job, restart counter is at 56.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit UNIT has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Nov 20 08:21:12 server systemd[1172]: Stopped Tracker file system data miner.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit UNIT has finished.
--
-- The job identifier is 2508 and the job result is done.
Nov 20 08:21:12 server systemd[1172]: Starting Tracker file system data miner...
-- Subject: A start job for unit UNIT has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has begun execution.
--
-- The job identifier is 2508.
Nov 20 08:21:12 server systemd[1172]: Stopped Tracker metadata database store and lookup manager.
-- Subject: A stop job for unit UNIT has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit UNIT has finished.
--
-- The job identifier is 2493 and the job result is done.
Nov 20 08:21:12 server systemd[1172]: tracker-store.service: Start request repeated too quickly.
Nov 20 08:21:12 server systemd[1172]: tracker-store.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Nov 20 08:21:12 server systemd[1172]: Failed to start Tracker metadata database store and lookup manager.
-- Subject: A start job for unit UNIT has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has finished with a failure.
--
-- The job identifier is 2493 and the job result is failed.
Nov 20 08:21:12 server tracker-miner-f[167547]: Set scheduler policy to SCHED_IDLE
Nov 20 08:21:12 server tracker-miner-f[167547]: Setting priority nice level to 19
Nov 20 08:21:12 server tracker-miner-f[167547]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location.
Nov 20 08:21:12 server tracker-miner-f[167547]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location.
Nov 20 08:21:12 server tracker-miner-f[167547]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location.
Nov 20 08:21:12 server tracker-miner-f[167547]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location.
Nov 20 08:21:12 server tracker-miner-f[167547]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location.
Nov 20 08:21:12 server tracker-miner-f[167547]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location.
Nov 20 08:21:12 server tracker-miner-f[167547]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location.
Nov 20 08:21:12 server tracker-miner-f[167547]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location.
Nov 20 08:21:12 server tracker-miner-f[167547]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location.
Nov 20 08:21:12 server dbus-daemon[1215]: [session uid=1000 pid=1215] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.119' (uid=1000 pid=167547 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Nov 20 08:21:12 server systemd[1172]: tracker-store.service: Start request repeated too quickly.
Nov 20 08:21:12 server systemd[1172]: tracker-store.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit UNIT has entered the 'failed' state with result 'exit-code'.
Nov 20 08:21:12 server systemd[1172]: Failed to start Tracker metadata database store and lookup manager.
-- Subject: A start job for unit UNIT has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit UNIT has finished with a failure.
--
-- The job identifier is 2523 and the job result is failed.
Nov 20 08:21:48 server sudo[167559]: administrator : TTY=pts/0 ; PWD=/home/administrator ; USER=root ; COMMAND=/bin/journalctl -xe
Nov 20 08:21:48 server sudo[167559]: pam_unix(sudo:session): session opened for user root by administrator(uid=0)
the error log that this gives me is
[2020-11-20 08:23:30 -0600] [167639] [DEBUG] Current configuration:
config: None
bind: ['unix:/run/gunicorn.sock']
backlog: 2048
workers: 3
worker_class: sync
threads: 1
worker_connections: 1000
max_requests: 0
max_requests_jitter: 0
timeout: 600
graceful_timeout: 30
keepalive: 2
limit_request_line: 4094
limit_request_fields: 100
limit_request_field_size: 8190
reload: False
reload_engine: auto
reload_extra_files: []
spew: False
check_config: False
preload_app: False
sendfile: None
reuse_port: False
chdir: /media/Storage/sales_portal
daemon: False
raw_env: []
pidfile: None
worker_tmp_dir: None
user: 0
group: 0
umask: 0
initgroups: False
tmp_upload_dir: None
secure_scheme_headers: {'X-FORWARDED-PROTOCOL': 'ssl', 'X-FORWARDED-PROTO': 'https', 'X-FORWARDED-SSL': 'on'}
forwarded_allow_ips: ['127.0.0.1']
accesslog: /var/log/gunicorn/access.log
disable_redirect_access_to_syslog: False
access_log_format: %(h)s %(l)s %(u)s %(t)s "%(r)s" %(s)s %(b)s "%(f)s" "%(a)s"
errorlog: /var/log/gunicorn/error.log
loglevel: debug
capture_output: False
logger_class: gunicorn.glogging.Logger
logconfig: None
logconfig_dict: {}
syslog_addr: udp://localhost:514
syslog: False
syslog_prefix: None
syslog_facility: user
enable_stdio_inheritance: False
statsd_host: None
dogstatsd_tags:
statsd_prefix:
proc_name: None
default_proc_name: sales_portal.wsgi:application
pythonpath: None
paste: None
on_starting: <function OnStarting.on_starting at 0x7fd62efa18b0>
on_reload: <function OnReload.on_reload at 0x7fd62efa19d0>
when_ready: <function WhenReady.when_ready at 0x7fd62efa1af0>
pre_fork: <function Prefork.pre_fork at 0x7fd62efa1c10>
post_fork: <function Postfork.post_fork at 0x7fd62efa1d30>
post_worker_init: <function PostWorkerInit.post_worker_init at 0x7fd62efa1e50>
worker_int: <function WorkerInt.worker_int at 0x7fd62efa1f70>
worker_abort: <function WorkerAbort.worker_abort at 0x7fd62efb20d0>
pre_exec: <function PreExec.pre_exec at 0x7fd62efb21f0>
pre_request: <function PreRequest.pre_request at 0x7fd62efb2310>
post_request: <function PostRequest.post_request at 0x7fd62efb23a0>
child_exit: <function ChildExit.child_exit at 0x7fd62efb24c0>
worker_exit: <function WorkerExit.worker_exit at 0x7fd62efb25e0>
nworkers_changed: <function NumWorkersChanged.nworkers_changed at 0x7fd62efb2700>
on_exit: <function OnExit.on_exit at 0x7fd62efb2820>
proxy_protocol: False
proxy_allow_ips: ['127.0.0.1']
keyfile: None
certfile: None
ssl_version: 2
cert_reqs: 0
ca_certs: None
suppress_ragged_eofs: True
do_handshake_on_connect: False
ciphers: None
raw_paste_global_conf: []
strip_header_spaces: False
[2020-11-20 08:23:30 -0600] [167639] [INFO] Starting gunicorn 20.0.4
[2020-11-20 08:23:30 -0600] [167639] [DEBUG] Arbiter booted
[2020-11-20 08:23:30 -0600] [167639] [INFO] Listening at: unix:/run/gunicorn.sock (167639)
[2020-11-20 08:23:30 -0600] [167639] [INFO] Using worker: sync
[2020-11-20 08:23:30 -0600] [167641] [INFO] Booting worker with pid: 167641
[2020-11-20 08:23:30 -0600] [167642] [INFO] Booting worker with pid: 167642
[2020-11-20 08:23:30 -0600] [167643] [INFO] Booting worker with pid: 167643
[2020-11-20 08:23:30 -0600] [167639] [DEBUG] 3 workers
[2020-11-20 14:23:38 +0000] [167643] [DEBUG] GET /opportunities/products/
That's all the information that I can think to include. If you think anything else would be helpful, just let me know. Just to reiterate, this exact setup was working until last Friday. I didn't change anything last Friday to make it stop working, that I know of. I changed a uuid in my fstab file for an unrelated hard disk, in my opinion, that should not have resulted in this behavior. Any help is appreciated. Hopefully I'm overlooking something simple.
Thanks,
Jonathan