Windows could not start DBConsole for new database instance [closed] - windows

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am getting this error:
Windows could not start the OracleDBConsoleOracleInstance2 on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the system vendor, and refer to service-specific error code 1
I installed Oracle 11g on Windows 7 and created my 1st database instance (oracleInstance1) successfully with a listener and service configured. I could access this database using DBconsole URL: https://localhost:1158/em.
I see the services started for:
OracleDBConsoleOracleInstance1
OracleOraDb11g_home1TNSListener
OracleServiceOracleInstance1
Next, I created a second database instance (oracleInstance2) and have configured a new service for this database. I am using the same listener as I intend to use one database instance at any point of time.
However, I got this warning message during configuration:
Enterprise manager configuration succeeded with the following warning - Error starting Database Control. Please execute the following command(s).
1. Set the environment variable ORACLE_UNQNAME to Database unique name.
2. C:\Oracle\product\11.2.0\dbhome_1\bin\emctl.bat start dbconsole
To start the new database console, I stopped the previously running DBConsole, OracleDBConsoleOracle1 and started the new DBConsole OracleDBConsoleOracle2 and get the above error.
When I try to start dbconsole manually using emctl dbconsole start, it starts OracleDBConsoleOracle1 instead.
I changed environment variables ORACLE_SID=oracle2 and ORACLE_UNQNAME=oracle2
What am I missing here?

Are you sure your env vars are applied correctly? If you set them in a DOS window then they'll only be visible there, you need to set them in the windows 'environment variables' screen.

Related

Crontab and haproxy [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I have a strange behavior which i do not understand:
I'm running haproxy as loadbalancer and security shield in front of other web containers.
The haproxy is running fine and uses my configured letsencrypt file.
So far so fine.
When the ssl certificate is running out, a new one including all needed key files is generated and replaces the key files.
After that, the haproxy must reload its config.
Now: when i call
cd /etc/haproxy
service haproxy reload
or the script itself from commandline, everything runs absolutely fine.
As soon as i call it via cron, it doesn't work!?!?
There is no error, and the reconfigure script is run till its end.
/etc/haproxy/bin/request_letsencrypt_certificate.sh:
#!/bin/bash
cd /etc/haproxy
service haproxy reload
crontab -e as root:
# LetsEnrcrypt | recert
* * * * * /etc/haproxy/bin/request_letsencrypt_certificate.sh
(i changed to run every minute for testing purposes)
When using echo test>run.txt the file is created every minute, so the script is started successfully, but the service command seems to be not executed?
What could be thy problem, why on commandline it works, but from cron not?
Both action are taken with root permissions as root itself (and when dumping the user in cron-call via whoami in the script, "root" is confirmed at runtime)
Does it work if you change service to /sbin/service to ensure that it's in the PATH? You also probably don't need cd /etc/haproxy in the script.

Pod going in crash back loop [closed]

Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 1 year ago.
Improve this question
I was trying to deploy my application in one environment. The pod is going in crash back loop with the below error:
"mdc":{},"timestamp":"2021-06-01
09:38:03.582","level":"ERROR","logger":"org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter","message":"\n\n***************************\nAPPLICATION
FAILED TO START\n***************************\n\nDescription:\n\nField
bac in
com.anjana.ms.anjana.ouseph.resources.services.implementation.anjanaValidator
required a bean of type 'anjana.wrapper.IBAC' that could not be
found.\n\nThe injection point has the following annotations:\n\t-
#javax.inject.Inject()\n\n\nAction:\n\nConsider defining a bean of
type 'anjana.wrapper.IBAC' in your configuration.\n","exception":""}
The application is getting successfully deployed in another environment, Why does it show two different behaviors in different environments, Jenkins build and Junits are running successfully.
Your spring-boot application cannot start successfully that's why kubernetes tries to restart and make it work but fails again..
A CrashloopBackOff means that you have a pod starting, crashing, starting again, and then crashing again.
You have a misconfiguration in your application, checkout similar problems like this 'Field required a bean of type that could not be found.' error spring restful API using mongodb

How to start automatically and run tomcat 6.0.37 version as a background process on Remote Desktop Server start up?

Currently I am running tomcat 6.0.37 version (64-bit windows) on remote desktop server(OS-Windows2008/64-bit), please help me to find answers for the following questions.
QUESTIONS
Q1) How can I run tomcat 6.0.37 version(64-bit windows) as a background process, after closing the tomcat server command prompt window?
(Note : "Tomcat windows service Installer" is not applicable for my scenario.)
Q2) How to start Tomcat 6.0.37 version(64-bit windows) automatically when remote desktop server(OS-Windows2008/64-bit) starts up and also when remote desktop server(OS-Windows2008/64-bit) gets restarted?
Please help me regarding the above questions with step-by-step procedure and some useful information regarding above questions.
Thanks,
Ashwini
The short version is you can't. The problems you are describing are exactly the type of problems running as a service is meant to solve.
I can't think of any valid reason why a web application couldn't run as a service. I'd challenge the supplier of your application as to why they are making such a claim.
Meanwhile, I'd run Tomcat as a service anyway. If the app needs access to network shares then you'll need to run the service as a domain user with access to those shares and make sure you specify them using the full UNC path rather than mapped drives.
I found the Solution on "How to start automatically and run tomcat 6.0.37 version as a background process on Remote Desktop Server start up?"
Step 1: In Environment Variables, set variable name and variable value as
CATALINA_HOME and C:\Tomcat6
Step 2: Environment Variables, set variable name and variable value as
CATALINA_OPTS and -server -Djava.awt.headless=true -Xms384M -Xmx1536M -XX:MaxPermSize=5750M(according to usage of your RAM size)
Step 3: Once installed tomcat service installer by setting the username = xyz, password= xyz and role=xyz-gui,manager-gui.
Then, in right corner of your desktop screen will get a Tomcat server symbol to start and stop the service. Right click on the icon, choose configure---->Java tab and enter those according to your system RAM.
In Java Options text box:
-Djava.awt.headless=true
-Xms1536M
-Xmx3072M
-XX:MaxPermSize=5750m(according to ur RAM size)
And set the values of:
Initial Memory Pool = 64MB
Maximum memory Pool = 5750(usage of RAM Size)
Thread Stack Size = 256MB
These steps are working perfectly for me. Tomcat service is running successfully without any problems.
Thanks,
Ashwini

Queued Build is not connecting to db as it uses domainName\computerName instead of domanName\username

I am trying to queue a build in my own build definition. But the sql connection in my code throws an exception that Login failed for user 'domainName\computerName$' which is natural since it should have used domainName\userAlias.
My question is why is it using domainName\computerName, and how to make it use windows auth instead? Can some one please help me with this?
You need to set the service account that the build service uses on the server(s) running your Build Agent(s). It sounds like it's currently set to run as Network Service.
You can change it by firing up TFS Admin Console, and going to Build Configuration and changing the properties on the service:

How to start and stop an "Automatic" process [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about programming within the scope defined in the help center.
Improve this question
I have an "automatic" mode process say "BPSAuto".
I need to keep thi process shut for certain time and later restart it.
I used bat file and sheduled the task to stop and start.
I used -->net start BPSAuto --- To start
And --> net stop BPSAuto --- To stop.
Now my problem is once I stop the process it again starts automatically. May be this is because it is in "Automatic" mode. Plesae help me to stop completely. And later restart.
Thanks in Advance...
sc config ServiceName start= <setting string>
note the space between start= and the setting for the service
Setting string can be one of:
boot
system
auto
demand
disabled
from sc config /?:
Modifies a service entry in the registry and Service Database.
SYNTAX:
sc config [service name] ...
CONFIG OPTIONS:
NOTE: The option name includes the equal sign.
type= <own|share|interact|kernel|filesys|rec|adapt>
start= <boot|system|auto|demand|disabled>
error= <normal|severe|critical|ignore>
binPath= <BinaryPathName>
group= <LoadOrderGroup>
tag= <yes|no>
depend= <Dependencies(separated by / (forward slash))>
obj= <AccountName|ObjectName>
DisplayName= <display name>
password= <password>

Resources