I accidentally delete /tmp in Weblogic 12c, does it affect the application performance or functionality?
If you are referring to the server tmp directories (ie. $DOMAIN_HOME/servers/SERVERNAME/tmp) then yes, you could run into errors, but these should be solved by restarting that WebLogic instance.
So if possible, restart at an oppertune moment.
Related
If so, how?
And how to check wether they are running?
Is there something like the manager for tomcat?
I have an Apache Server running, that has been installed automatically by a package installation routine. I expect that the routine installed OpenProject on the server. But I cannot point to the application.
So I don't know wether OpenProject is not installed, not started or pointing to it with
http://185.82.22.144:80/OpenProject
is wrong.
The installation routine seemed to work fine, with no error messages.
peter
No, because the way you are using language implies that you are asking about functionality which is exposed by the Apache server - but that functionality is not "in" the webserver, apache merely provides a means for accessing it.
I'm installing uberSVN on an Ubuntu server with an existing Apache installation. Rather than using uberSVN's built-in Apache server on a different port to access the SVN repositories, I'd like to use a vhost on the currently running one.
Are there any ways I can achieve this?
As uberSVN is meant to be able to run 'out of the box' it will use it's own instance of Apache even if you have another one already installed. This is not something configurable (at least not from the UI), and is not recommended to be changed as it can cause problems if there are different uses or port conflicts. Is there a specific reason that using uberSVN's instance is an issue?
I just wanted to know if memcache is linked to apache or it runs as a separate process. So, will restarting apache clear my memcache contents or not?
You can also empty memcached without restarting it:
telnet localhost 11211
11211 it the default port for memcached (if nothing responds on this port check your init script)
And within telnet:
flush_all
This will flush all stored data.
No. Memcache is not linked to the apache process. Memcached is a separate process.
HOWEVER, your application framework if you are using one, may flush memcache if you restart apache.
-daniel
restarting the server will flush all stored data
/etc/init.d/memcached restart
We are running Weblogic 7sp6. We have a working single node cluster with an Admin and two Managed servers. We are re-creating a 2nd standalone cluster on a 2nd server. We reinstalled Weblogic and have copied over all the configuration files to make thing. Its the same on both clusters. We changed all the references to IP and hostnames. We have used this method before without problems.
In the current case I can startup the Admin which listens on port 7001,7002. But when I try and startup either of the Managed servers it tells me that myserver1/2 is already up. (Managed Servers). I confirmed that myserver is configured to use port 7012,7013 and I cannot find any port conflicts especially because these exact ports worked on the first cluster. Any ideas of what else to look at? I have logged in the admin console and can see the ports are all unique. Thanks
The current version of WebLogic is 10.3. I'd strongly urge you to upgrade your WebLogic as soon as possible, especially if you're still using the version of JDK that it was certified for. If you're running JDK 1.4, you're crazy.
My Apache server works fine without -DSSL, but does not start with SSL. This happened after I re-install the certificate because of expiration. (it used to work before) I would love to have some tool to check up if my newer setup of ssl key and certificate is correct or not. That would include permission, ownership etc..
Or is there any way to figure out why it doesn't work with SSL?
You can check your configuration files for syntax errors without starting the server by using apachectl configtest or the -t command line option.
That said, I don't think that Apache fails silently. There must be something in Apache's logs. Can you check this and provide the trace?
PS: You should add details on your environment such as your OS (Windows, GNU/Linux, Unix, etc), the Apache version, etc. This could help.
I would suggest, https://globalsign.ssllabs.com/ if your website is publically available.