Error - mongod shell doesn't start, /data/db doesn't exsist

Error - mongod shell doesn't start, /data/db doesn't exsist


If you face this error while starting MongoDB (mongod), most probably there are 2 reasons for this -

a.  /data/db is not exist at all
b. mongod process don't have access on /data/db

Solution :-

The default db path for mongodb is /data/db/.
So when you run:

MongoDB is unable to start due to lock file

While starting MongoDB server, You are facing that MongoDB is not getting up with a exception says -

Sun Jan 18 12:27:03.884 [initandlisten] exception in initAndListen: 10310 Unable to lock file: /data/db/mongod.lock. Is a mongod instance already running?, terminating
Sun Jan 18 12:27:03.884 dbexit:

Normally, we are facing this issue due to 1. improper MongoDB server shutdown or 2. someone else is started the mongo server. In the second case, we dont have any issue, we can connect to out db without issue.

CentOS - Hostname Change

Hostname Change

There are 4 steps in a hostname change, luckily all the steps are easy.

Sysconfig/Network

Open the /etc/sysconfig/network file with your favorite text editor. Modify the HOSTNAME= value to match your FQDN host name.

Hosts File

Change the host that is associated to your main IPaddress for your server, this is for internal networking (found at /etc/hosts):

WebSphere Application Server[WAS] fails to start in Linux

The application server fails to start after system is restarted. No messages are generated in the application server logs.

The Metadata server startup script fails to finish. You must issue the nohup command for the Metadata server startup script.

Check to ensure that WebSphere Application Server is running.

To connect to the application server using an Internet browser:

1. Start your Internet browser.
2. Type the application server address in the form: http//isserver:portnumber, where isserver is the name of the computer where the services tier is installed or its tcp/ip address, and portnumber is the port for connecting to the services tier (by default, 9080).

If the application server has started, the login screen is displayed; otherwise an error message is displayed.

Failure to connect to DataStage services tier: invalid port

When you attempt to start one of the DataStage clients, the following message is displayed:

Failed to authenticate
the current user against the selected Domain:  Could not connect to
server [servername] on port [portnumber].

Unable to open jobs with error "Unable to open the Job Unable to load RID"

Unable to open jobs with error "Unable to open the Job Unable to load RID - c2e76d84.43058877.7e01af4f.cd92bbcd-2ebc-4cb3.833e.37a962373ef7"

Also in SystemOut.log file, it has the following:
[8/25/10 21:21:46:475 UTC] 000000b1 SystemOut O 2010-08-25 21:21:46,475 ERROR ojb.OjbPersistentEObjectPersistence - java.lang.OutOfMemoryError

Clean ReStart of the IBM InfoSphere DataStage Engine

If you suspect some Client sessions did not cleanly end or disconnect, you can perform a clean restart to make sure the DataStage Engine is starting from scratch. Please make sure all clients are logged off and no jobs are running before performing the below steps.

Here are the instructions for a clean restart of DataStage Engine:

How to start/stop the DataStage Services in Windows with batch (.bat) file

Hi Friends

Normally, When we install the datastage in Windows, It installed a Service in Control Panel called “DataStage”. For stopping and starting the DS services we have to double click on it and press the button Start/Stop. 

As this is not open with the admin rights, you can face the issue while starting or stopping the services like – Access Denied.

How to restart DataStage ?

Hi Friends, today I am going to share how to restart the server, what are the steps we have to take care while performing this task.

The order in which to stop all services is:

   1. Stop DataStage Engine
   2. Stop the ASB Agent
   3. Stop the WebSphere Application Server (WAS)


Here are the step-by-step instructions for each of the above.