Thursday, 28 February 2008

VMNet1 not up after Hibernate

The vmnet configuration of VMWare Server in (Ubuntu)Linux is quite rudimentary. It is done using a script whereas in Windows you'll lucky to have a nice configuration screen.
I regularly just wrap-up my wrap-box (in Dutch I tend to call my notebook 'klapdoos') after work. I configured it such that it will hibernate my Linux.
But after resume I experienced that the VMNetwork is not up. That is quite inconvenient, because I would have to restart my machine and then suspend or start my VMware images. I need the VMNet1 (host only) often because I let several VM's work together and I connect to the machines using jDeveloper, sqlDeveloper, etc. from my host. Or Pl/Sql Developer on another VM.

Luckily I found on an Ubuntu forum a simple command to startup the vmnet's again:
ifconfig vmnet1 up

So I created a simple script VMNetup:
ifconfig vmnet1 up
ifconfig vmnet8 up

I put the script in /usr/lib/vmware/lib and added the command
"sudo /usr/lib/vmware/lib/vmnetup" to my System Tools menu. I set the type on 'Application in Terminal' since I have to give in a password for the sudo command.

Now with a simple menu click and a password my problem is solved.


Marco Gralike said...

"init.d" ?

Valéria Magalhães said...

Thank you, you resolved my problem :-)

Anonymous said...


I am using Oracle BPM11g virtual box. While I am trying to create a datasource in weblogic console. I am getting below error.

Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error weblogic.application.ModuleException:
Message icon - Error Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

When I am testing the DB connection, I m getting a success message. But When I am activating changes I am getting above error. Please help.I am able to connect to DB in Jdeveloper.

I tried searching in previous posts but I couldn't get. Please help.


Martien van den Akker|Darwin-IT said...

Hey Anonymous,

If you logon on the database on the console of the os, then you might bypass the listener.

You could check the listener.ora and tnsnames.ora in /network/admin. Make sure the entries there refer to a hostname that point to a correct ip-address.

Then with "lsnrctl status" you can check if the listener "knows" the database.

And finally start the listener before the database.