Developed a web application in Struts Frame work , But I am unable to Login to the application which is installed on a Turn Key Linux System. But the application is still running smoothely on my local Machine and also tested in few other machines also . I am only facing this login problem in this Turn key linux system only.
I am installing this application usind a MyApp.war with default user (username=user and password = user)
database - Java Derby
Downloaded turnkey-zimbra-2009.10-2-hardy-x86. From vSphere Client selected to "Deploy OVF Template" and navigated to turnkey-zimbra-2009.10-2-hardy-x86.ovf file using the deploy from file option. This error comes up immediately:
I have had a look around the forums and not found exactly what i want but please advise if i have missed it.
I just dicivered Turnkey Linux and it is a life saver for me now however I have loaded Turnkey LAMP onto a VPS and use this for a small business intranet which has various databases on it.
So i back the SQL every day however i would like to replicate this onto a USB drive , so say either the server goes down or the comany looses internet access at least they then have access via the usb srick temporariliy.
I am hoping someone can help this init script newbie.
For my init script I would like to switch to a different user account for security reasons. Using the start-stop-daemon I have used the "--chuid" option to switch users.
This works fine however I have found that the user account does not make use keychain for ssh connections.
Is this normal behaviour for the start-stop-daemon?
To work around this issue I have just created a seperate wrapper script "invoke_app" that manually calls keychain and then invokes the application.
All was working fine, until I reset the computer (Turnkey LAMP running in VMWare Server) and now it cannot get a lease from any DHCP server and setting a static IP does nothing.
There are 2 errors in startup that I am not sure whether were always there:
Host SMBus controller not enabled!
and
udhcpc[3560]: SIOCGIFINDEX failed!: No such device
The latter is more likely to be the problem, but it eludes me why it would start to produce error after a simple restart.