I have configured our managed servers (on WebLogic 10.3.5) to use SSL with custom identity/trust keystores and all that has been working fine. However, after completing the SSL configuration, we started getting some warning messages saying "Invalid/unknown SSL header was received from peer". After looking through some articles online, the solution seemed to be setting the SecureListener property in nodemanager.properties to "false" and setting the listener type of the Node Manager in the Administration Console to "Plain". This did stop the warning messages from showing up in the log file...however I was wondering if there are any security implications to using a plain vs. SSL listener for the Node Manager. FYI, this is a development environment that's closed off from public access but will eventually be moved to a production environment.
Brian's questions
I administer several Linux-based servers and we are looking at migrating several JBoss apps as well as a couple of websites running on Apache from a RHEL 5.5 (64-bit) server with 4 cores to a RHEL 6 (64-bit) server with 24 cores. My supervisor has mentioned the possibility of using cgroups to manage memory/CPU allocation on the new server. I've done some reading/research on my own and have a fairly good understanding of the purpose of cgroups and what they can do.
My question is, what would be the advantages of running cgroups and is this an effective way to manage JBoss applications?
I've installed SSH Secure Shell and xming on my laptop running Windows 7 (64-bit). I'm having trouble starting X Windows applications from the SSH console. I've been able to do it in the past. I've pretty much determined that it's not a server issue because I've tried it on two different servers (both servers are running RHEL 5).
Running "echo $DISPLAY" on either server gave me "localhost:10.0".
My XLaunch configuration settings are: Multiple Windows, 10 (display number), and Start no client. Once xming has launched, I'll try to execute something like "firefox" and I get this back:
The application 'firefox' lost its connection to the display localhost:10.0; most likely the X server was shut down or you killed/destroyed the application.
I've already checked to make sure that the X server is running and it is:
root 12579 2689 0 Feb14 tty7 00:04:23 /usr/bin/Xorg :0 -br -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7
Additionally, X11 Tunneling has been enabled in SSH as well as SSH 2 connections.
When I try to execute
/etc/init.d/xinetd start
I get the following error:
Starting xinetd: /bin/bash: /usr/sbin/xinetd: cannot execute binary file [FAILED]
Also, if I check the status of xinetd, I get the following output:
xinetd dead but subsys locked
--
Server details:
Linux xxx.xxx.xxx.edu 2.6.18-194.11.3.el5 #1 SMP Mon Aug 23 15:49:21 EDT 2010 i686 i686 i386 GNU/Linux
/usr/sbin/xinetd
produced:
bash: /usr/sbin/xinetd: cannot execute binary file
--
stat /usr/sbin/xinetd
produced:
File: `/usr/sbin/xinetd' Size: 164144 Blocks: 336 IO Block: 4096 regular file Device: 802h/2050d Inode: 392043 Links: 1 Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2011-04-08 09:27:58.000000000 -0400 Modify: 2011-04-06 17:04:35.000000000 -0400 Change: 2011-04-06 17:06:21.000000000 -0400
I'm attempting to test out the check_mysql plugin for Nagios using the command line. It works great when I'm just checking localhost but when I try to specify a different server (using the -H argument) I keep getting the following error message:
CRITICAL - Unable to connect to mysql://nagios_user@{remoteServerHostname}/ - Access denied for user 'nagios_user'@'{localServerHostName}' (using password: YES)
It looks like it's trying to connect to the database using the localhost server even though I've specified a different host name. I've already set up this user on the remote database and they have correct permissions. I'm just trying to figure out why the script keeps inserting the localhost server name instead of the remote one.
I have installed MySQL
on a RHEL 5 server
and I want to set it up so that the server starts on boot.
I've ran the chkconfig --list mysqld
command and it's currently running on levels 3, 4 and 5. However, when I reboot the server, no mysqld
daemon is started.
I've also tried manually starting the server by executing /usr/bin/mysqld_safe
and I get the following output:
Starting mysqld daemon with databases from /var/lib/mysql
STOPPING server from pid file /var/run/mysqld/mysqld.pid
100319 10:31:30 mysqld ended
I looked in /var/log/mysqld.log
and I found the following:
100319 10:29:01 mysqld started
100319 10:29:02 InnoDB: Started; log sequence number 0 29752204
100319 10:29:02 [ERROR] Can't start server : Bind on unix socket: Permission denied
100319 10:29:02 [ERROR] Do you already have another mysqld server running on socket: /var/lib/mysql/mysql.sock ?
100319 10:29:02 [ERROR] Aborting
UPDATE: I tried starting using the mysql.server
script (from /usr/share/mysql
) and it worked.So I went ahead and linked this script to the appropriate run levels (rc0.d
, rc3.d
and rc5.d
). However, it's still not starting on boot.
I'm having issues running an X Windows session on a RHEL5 64-bit server - whenever I execute the command "gnome-session &", the process goes into the background but nothing happens. I have Exceed installed on my Windows machine which is running when I try to start the gnome-session. I've tried just starting firefox by itself instead of the whole gnome session, but it doesn't work either. Any suggestions?
BTW, here's the error message I get when I try to start firefox:
firefox: Fatal IO error 104 (Connection reset by peer) on X server localhost:10.0.
I have deployed an application using JBoss 4.2.2 on a 64-bit RHEL5 server. Since there are other JBoss servers, I had to change some port configurations so that there would be no conflicts when starting the server. So right now I'm using ports-01 from the sample-bindings.xml file that came in the docs/examples/binding-manager/samples directory. In addition, below is a list of all the files I've edited to reflect the new ports:
- JBOSS_HOME/servers/default/deploy/jboss-web.deployer/server.xml:
- Changed Connector port - 8080 to 8180
- Changed AJP 1.3 Connector port - 8009 to 8109
- JBOSS_HOME/server/default/deploy/jbossws.beans/META-INF/jboss-beans.xml
- Changed 8080 to 8180
- JBOSS_HOME/server/default/conf/jboss-service.xml:
- Changed 8083 to 8183
- Changed 1099 to 1299
- Changed 1098 to 1298
- Changed 4444 to 4644
- Changed 4445 to 4645
- Changed 4446 to 4646
- Changed 4447 to 4647
- JBOSS_HOME/server/default/conf/jboss-minimal.xml:
- Changed 1099 to 1299
- Changed 1098 to 1298
When I start the server (binding to localhost) everything is fine and I'm able to access the application. But when I try to shutdown the server I get the following error:
Exception in thread "main" javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost [Root exception is javax.naming.CommunicationException : Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]]] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1562) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.Shutdown.main(Shutdown.java:214) Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533) ... 4 more Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:248) ... 5 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:525) at java.net.Socket.connect(Socket.java:475) at java.net.Socket.(Socket.java:372) at java.net.Socket.(Socket.java:273) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:244) ... 5 more
Is there any other file that I need to change the 1099 to 1299, or am I missing some other step?
I am attempting to install glibc-2.5.34.i386.rpm on RHEL 5 (necessary in order to install gcc, which in turn is needed to install Apache server). I mounted the RHEL 5 iso to /mnt and copied over the relevant RPM files to a separate directory). When I run rpm -ivh glibc-2.5-34.i386.rpm I am getting a dependency error stating the following:
error: Failed dependencies: glibc-common = 2.5-34 is need by glibc-2.5-34.i386
Okay, so I grabbed the glibc-common RPM from the RPM fiinder site and ran rpm -ivh on it. However, it complains that I have a newer version of glibc-common package installed (2.5-34.el5_3.1.i386) and then spits out a bunch of lines about conflicting files. So is there a way to somehow uninstall or rollback glibc-common to version 2.5-34 so that I can go ahead with the install of glibc?
Btw, I cannot use yum due to network connectivity issues.
I just recently installed RHEL 5 on a virtual machine. The server is set up to use a static IP, which I've configured in the Network Configuration GUI. There is only ethernet interface set up called eth0 which is set to activate on boot. After restarting Linux, I went to check to make sure that it was indeed activated, but it wasn't so I manually activated the device.
Going into the command line, I tried:
- Iinging google.com but got 100% packet loss.
- Pinged the IP address of the router the server is using for the gateway (set in Network Configuration Manager), which came back with 0% packet loss.
- I tried pinging the IP address of the server itself, which again came back with 0% packet loss.
However, if I try opening up Firefox and navigating to a site, nothing will come up. Any suggestions?
UPDATE 1: When I ping www.google.com, I don't get "Unknown host", so the DNS should be fine.
Following Matt's advice, I issued the command route -n and got the following output:
> Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.X.X.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 10.X.X.1 0.0.0.0 UG 0 0 0 eth0
UPDATE 2: After issuing the command:
traceroute -n www.google.com
I am seeing IP addresses for #1 and #2, but the rest of them have three asterisks where the IP addresses should be. Plus, I couldn't even connect to www.google.com using the telnet command. So it does look like a network firewall is most likely causing the problem. I think that's about all the information I can provide until I can confirm whether or not the cause is indeed a firewall.