I want to run a script to start pg_dbms_job scheduling automatically after Postgres server is started successfully.
Is there any solutions to resolve this problem?
Thank you
Related
We are running MongoDB as docker container and all of sudden it become unresponsive. We had tried to restart container but it didnt. The docker restart command was success but if we check the service it didnt restarted. We are not able to connect to DB from our Mongo client too.
After full VM restart the problem got solved. I would like to know if anyone has faced this issue and got any solution for it.
Here is the details my docker:
Docker version 19.03.12
Mongo 4.0
I am running postgresql in a docker container. Now I wanted to add checksums to the database cluster. So I stopped the docker container and waited some time. But the pg_checksums tool is still complaining:
pg_checksums: error: cluster must be shut down
There is no postgres or similar running any longer, with docker or not.
Renaming the file postmaster.pid did not change anything.
What du I need to do to convince pg_checksums that it can savely work on the cluster data?
I'm using postgresql 12 and Docker version 19.03.13, build 4484c46d9d on a CentOS 8 machine.
You need to shutdown the database cleanly. Shutting down the container itself apparently did not do that. A tool which does not attach to PostgreSQL's shared memory has no way to know whether a database has crashed, or is still running. So you need a clean shutdown.
I'm trying to run juinit on a remote postgresql docker.
I tried to use testcontainers.org but I can't get the configuration to work
I keep getting timeout exception
Does testcontainers support such setup? if so is there an example for that?
Thanks
as long as you have your Docker configured correctly, it should work out of the box without any additional configuration.
Just make sure that your environment variables point to the remote Docker daemon.
Aem Author instance is not coming up after the automatic backup process. We have automatic backup process scheduled daily at 10:00 Pm PST. We are running a Shell script(backuprepo.sh) which in-turn triggers the stop.sh to bring the server down, do the backup process and then trigger the start.sh script to start the instance again.
The instance is brought down, but sometimes it is not started with the start script and has to be started manually. We have noticed that the below crx java process is not killed when the server is stopped though the stop script.
adobeam6 8454210 1 2 22:27:57 - 187:34 java -server
-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xmx4096m -Doak.queryLimitInMemory=500000 -Doak.queryLimitReads=100000 -Dupdate.limit=250000 -Doak.fastQuerySize=true -XX:MaxPermSize=512M -Djava.awt.headless=true -javaagent:/app/AEM6/author/crx-quickstart/app/newrelic/newrelic.jar -Djava.io.tmpdir=/app/AEM6/author/tmp -Duser.timezone=America/Los_Angeles -Dsling.run.modes=author,sit -jar crx-quickstart/app/cq-quickstart-6.0.0-standalone.jar start -c
crx-quickstart -i launchpad -p 4502
-Dsling.properties=conf/sling.properties
So we have to manually kill the process and trigger the start script to start the instance. Trying to figure out why the server is not stopped properly sometimes and why the above mentioned process is not killed even when the server is stopped through stop script.
We have verified the error logs which only stated the Instance has stopped as last Info.
Below are the steps executed by the backuprepo.sh script:
1)Trigger the stop.sh script
2)Wait for the server to stop automatically and backup process to complete.
3)After the backupprocess is complete, check if the server is started automatically.
4)Sometimes the server is not started automatically which is the issue.
Attached the start.sh and stop.sh scripts.
https://drive.google.com/open?id=0B67j43IdLr8mLXVCWTYxd1NialE
https://drive.google.com/open?id=0B67j43IdLr8mbDNPWndRdE5SWEE
Question:
Do we have any scenarios when we stop the AEM server, the crx java background process would still be running?
Any clues for our case which is preventing the java process to be release when the stop script is triggered?
I installed MySQL and was playing around with the password settings trying to get Wordpress to connect to it. In doing so, I seem to have hashed my root password and now cannot login.
I'm trying to reset the password by running
/etc/init.d/mysqld stop
Then
mysqld_safe --skip-grant-tables
Which outputs
Starting mysql daemon with databases from /var/lib/mysql
But then does nothing. It neither succeeds nor fails. I've not got any databases setup so I'd be happy to remove and reinstall mysql if necessary but I tried that to no avail. How can I get back in?
mysqld_safe is the command to start the mysql engine. It's not supposed to do or show anything after the line saying that it's started mysql. Once you've run mysqld_safe, the next step is to run mysql. Because you started mysqld with --skip-grant-tables you won't need to specify a username or password.
You can then give the command to reset root's password. For instructions on how to set a password, see http://dev.mysql.com/doc/refman/5.0/en/set-password.html .
have you tried "mysqld --skip-grant-tables" instead of mysqld_safe? make sure to kill any mysqld threads that didn't die before starting mysqld --skip-grant-tables. Do a ps -ef and grep for mysql, kill -9 any mysql process, then start it --skip-grants-tables.