I've gotten myself involved in the Nagios monitoring tools and somewhat managed to configure the Nagios host, but I'm still having some issues with the email notifications.
From what I've read/researched, one of the favourite methods to get the email notification up is by using sendmail/postfix. I've went through it and learned that they are MTAs. What I actually needed is just a basic email client, and I would email the notices directly to an email address over the internet. Thus, I wont be needing something as complex like sendmail/postfix.
I gotten my hands on "Nail mail". I've successfully configured it to be able to send emails from my linux machine over the internet. However, when I copied the same command lines to nagios's contact.cfg, it did not work.
This is the command line that I'm using. Let me explain what I'm trying to achieve below. Firstly, I would save all the text notifications into a text file(green), and then email it out. The problem is NailMail command (red) does not work on Nagios,but the command line works in the terminal command on my Nagios account. Has anyone attempted using Nail mail with Nagios?
I have a script that sends short reports via the mailx command which is failing a lot lately.
Syntax used is basically: mailx -s "the subject" -r firstname.lastname@example.org email@example.com < textfile.txt
For what ever reason this command has become very unreliable lately. I've tested on the command line and sometimes it works but frequently fails. The -r address seems to cause problems as it always fails with a -r set to my work address. I've read several theads and tried adding a .mailrc file but couldn't get past the NSS configuration setting. (Using my mozilla x123x.default dir results in Error initializing NSS: Security library: bad database. )
The nail command behaves about the same. what would make email sending so intermittent?
I've checked the /var/log/maillog but see each mail session end with the following and no errors reported:
I've got a machine running Ubuntu Server that is on several VLANs. Each VLAN has its own subnet and the server has an address on each subnet. The switches are set to allow tagged traffic to the server for each VLAN that it is on. Switch ports ending with workstations are given untagged ports on whatever VLAN is appropriate. Workstations are given addresses on a subnet for each VLAN via DHCP. All this works great and hosts on any subnet/VLAN can access the server as normal via its address on that subnet/VLAN.
Accessing the machine by its address on a non-local subnet is where I run into a problem. Inter-subnet traffic has to go through a router, which has been set up appropriately. Running tcpdump on the server and pinging it from a workstation on a subnet, using its address on a different subnet, shows the server receives the ping, but sends no response:
Code: sudo tcpdump -i vlan4 -n tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
There are 5 copies of the same images are placed in a folder i.e. large(1024*768),medium(500*375),small(240*180),thu mnail(75*75),square(100*50) in size....
The following code upload number of Geocoded images(square size) when the page loads.I want when someone click on the any Geocoded image on the page ,it should show the large image(1024*768) of the same.And further click on the large image it must show again the square size image of the same.
I am connecting servers using NFS4 the shared directories are on servers running Debian 4 while the one who read from them is Debian 5.0.3. The problem is one of these shared servers suddenly stop responding and you cannot list it from Debian 5 server, also df hang, and the web application that is using it does not respond to requests that use this shared directory since it is blocked. Then the load on the server start to increase until the server cannot respond (over 90). I have found many entries in the syslog that refer to this like:
ma25555 kernel: [1200285.732919] nfs: server 10.xxx.xxx.xxx not responding, still trying Dec 31 08:16:33 ma25555 kernel: [1200289.815378] INFO: task java:9702 blocked for more than 120 seconds. Dec 31 08:16:33 ma25555 kernel: [1200289.835249] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. code....
I have tried the connection between the 2 servers using ping for one day and all are OK (zero lost)
There are 3 other servers that are running Debian 4 and are working fine.
5.5 (64bit). My server goes into non responding state where I can't telnet, ftp or ssh server whereas PING is the only thing which works at that time. I need to hard reboot server to get it back online. This is happening very frequently in fact yesterday and today server went inaccessible. which log file should I look into to find out the reasons of this inaccessibility?
i m experiencing some problems connecting via ssh two ubuntu workstation: a ssh client and a ssh server The goal of that is to run from local client computer some X applications on the remote server machine
i have configured both client and server for X11forwarding (i think) properly Infact when i launch xeyes on the client i see the X app running
the problem is for all other X apps. For example when i run xclock, nothing happens on the local PC the prompt continues blinking without any reponse, no windows opens and the strangest thing, the shell is stucked. No possible to interrupt with [CTRL]+c the onyl thing to do is close the shell window
Starting in verbose mode (debug), X11 seems works correct , it says x11 confirm as last message .
I have a Mac G3 and Squeeze 2.6.32-5-686 on an ethernet wired. Works fine with Lenny kde but only in one direction with squeeze kde4. Mac pings squeeze box ok but response is "server may be down or offline". Squeeze connects to Mac normally. Squeeze installed with server option. How do I enable eth0? I need some direction
Currently have a problem with my LTSP server when using a gigabit switch with a megabit thin client.I am using K12LTSP with Fedora 9.The thin clients get most of the way through booting up then I get error messages saying:nfs: server 172.31.6.1 not responding, still trying.I don't get this problem if I use a 100 meg switch though.I have found several forum posts on the internet which all seem to point to the following webpage with a solution:However, when I make the recommended changes It doesnt make a difference.Below is an example of the default file located at /var/lib/tftpboot/ltsp/i386/pxelinux.cfg with its default settings:
I recently decided to install Ubuntu and I went through all of the steps to set up a subversion server using svnserve. It all works except for one thing: it stops responding to remote computers after a while.I have the server on a 4 port wireless router/switch in my dorm room. I set up port forwarding so that the server receives all traic over the correct ports. The subversion server AND the default http server on Ubuntu work fine always as long as I access them from a computer connected to the switch in my room.The problem is that if I try to access it from anywhere else, it won't respond at all unless it has been accessed by a computer on the switch recently (something like 30-60 minutes). So to fix it I have to go back to my room and access it from a computer on the switch. Then it will work from anywhere for another 30-60 minutes.
I have deployed proxy server in my office about a month ago. I have about 7-8 client accessing it through port 3128. After some days of deployment, my server started creating problems. Some clients were not able to access proxy while other clients were accessing it. The error message which I found in cache.log was:
Code: WARNING: Closing client 192.168.2.99 connection due to lifetime timeout
In this way it was disconnecting clients randomly. The problem resolves when I restart proxy server
Im sending my cache.log file
Code: Last login: Mon Nov 15 12:37:29 2010 from 192.168.2.2 [root@localhost ~]# cat /var/log/squid/cache.log 2010/11/15 08:11:49| storeDirWriteCleanLogs: Starting... 2010/11/15 08:11:49| Finished. Wrote 57740 entries.
after a update to 5.3 from 5.2 via the built in updater the system stops responding to visitors from the outside, http that is, but heres the odd part, if i say run firefox on the server the connection works also for some reason if i'm on the network with my own computer the connection seems to stay open but as soon as i stop using these the server seems to drop the conenctions, but as i said as soon as i go via my comp to the server via say ie it works right away.
this i tried yesterday:did a cold boot to see if some update had problems and actually needed a reboot even if the updater didn't say, after it started the connection seemed to be open for a good while, and not untill this morning from a outside source the connection is droped again, not been on my comp nor logged on on the server today yet.the install only has on it what i got from the dvd, and as far as i know it has all the updates on it since 5.3 came out.my network is built up like this:
I am running CentOS 5.2 on a server here in my home. It runs Dovecot and Postfix and also serves as a website host for a small website of mine. Everything works fine. POP, SMTP, Webmail, WWW, all works great and has for ages.Here's the issue. I recently reinstalled a clean copy of Windows 7 on a workstation in my home onto a new harddrive(I still have the old drive int he machine so I can boot to it as well). I setup the Windows Live Mail client to send/receive mail with my mail/web server. However, it won't connect to the POP server on my server machine.Here's the kicker. If I boot to the old harddrive that is running Windows 7, it connects fine to my mailserver and can send/receive just fine. I've checked, rechecked and rechecked and all mail settings on the mail clients on both drives are identical.
Note: The installations of Windows 7 on both drives is identical. Same computer name/ same credentials, same IP, etc. However, as I stated, I can send/receive email with my server if I boot to my old drive, but if I boot to my new drive, I cannot send/receive.
I am using CentOS 5.5 (64 bit) on a Quad core server having 8 GB RAM. This server has MySQL server 5.1.47 installed. THis server goes non responding state after every 20 to 60 days. SSH, telnet doesn't work at that time however PING works fine. I have to hard reboot the server to get it back on track. Can anybody let me know what logs/files should I look into to find out that what happens to the server when it went to non responding state?
As i've installed the new fedora update packets ,i've seemed to develope a strange networking problem .. Network description Fedora 15 with 3 LAN adaptors eth0 > LAN (IP address 192.168.0.254)eth1 > network connected to a pppoe conection eth2 > WAN to another provider. Ok so let's ignore eth2 because i've disable mangle(i was using trafic shifting on some ports). So now i'm using it as a simple NAT server .. so the problem is : >>my server is not responding to the traceroute command is it should .. the network works thou but this is what i get. C:UsersDUAL>tracert google.ro
I've been working on getting NoMachine and FreeNX working together ... and they're both working well, listening on different ports (guess I should write a howto). At some point I decided to write an init script to control FreeNX behaviour (start, stop, status, setup), since the Ubuntu version has one (called freenx-server) and openSUSE doesn't, but I noticed that it was not necessary, as FreeNX got started automatically... but how ? I could not find any init.d script or command which would start the FreeNX server. Indeed it wasn't actually running :
Code: neelix:~ # /usr/bin/nxserver --status NX> 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.2.0)
I've had a VPS running Ubuntu 9.10 x64 server, hosting 3 websites of mine for a few months now. This problem has been happening for a while. Every once in a while, probably every 2 or 3 days, I'll wake up in the morning, and apache won't be responding, no web pages will load. /etc/init.d/apache2 status, reports that apache is functioning properly. Every time I simply have to restart the daemon and things run fine for another few days.
I thought maybe it was a memory issue, so I lowered the MaxClients in the prefork module from 50 to 30 a few days ago, but the same thing is still happening. My VPS has 512MB of ram, burstable to 1GB, and according to Virtuozzo, there was only one night of high traffic where I even came close to that soft limit. I've checked my syslog, and there's absolutely nothing in there about apache. I've checked apache's error.log as well, and there's nothing in there that would indicate a problem either.
Server Distro: Debian Testing (Squeeze) FreeSWITCH ver.: 1.0.6
Client (Dual-Boot Setup) Problem: Both Windows Vista Ultimate 64-Bit and Ubuntu 10.04 LTS versions of Ekiga, including SFLphone in Ubuntu 10.04 seems to be ignored by FreeSWITCH. FreeSWITCH fails to register. In the client side, the Windows firewall gets turned off for testing while everything in iptables under Ubuntu has everything set to accept in the filter section. In the server side, the firewall configuration is quite basic.eth0: Cable Modem plugged in via USB cable eth1: nVidia Gigabit that connects to my 1Gbit switch
I am bit new to Linux and have setup caching-only name server with Centos 5.5. when i do dig server, it provide resolutions. but when i use the server IP as DNS on my windows client, it says, "connection refused" on the NSlookup output. (IP table didn't enable) My server Ip is 192.168.1.253 and bellow is the configuration of "/var/named/chroot/etc/named.conf"
I have installed bootpd-dd2 and enabled and configured it with xinetd. 1. Made sure that their is a bootptab file and it is configured. 2. Tested the bootpd is working by runing the command /usr/sbin/bootptest cmdbfs .3. tail -f the /var/log/messages and saw the requests from the test.4. rebooted a machine that is configured to pxe boot.there is no messages by bootpd when a request is made.request is picked up by network monitor on a seperate computer on the proper udp port
I have set up nfs-kernel-server on my Debian Lenny server and nfs-common on my Ubuntu 9.10 workstation as described here. Everything is generally working just fine, except that every time, when I start my workstation from suspend-to-RAM after more than a couple of hours of suspension, I can not access the NFS-shares (nautilus or ls in a terminal just hangs), and /var/log/messages shows "nfs: server NAME-OF-SERVERnot responding, timed out".
The problem is definitely not the server, because all I need to do to get it working again, is "umount -f /mnt/NFS-SHARE" followed by "mount /mnt/NFS-SHARE", or just wait some time (around 10-15 minutes) and then everything is fine again. I always only suspend-to-RAM, I usually do not turn of the machine completely. I have no explanation for that issue, but it must have something to do with being in suspend-to-RAM for a certain time. Pretty weird!
Strangely I never had this problem with NFS shares from a server running the FreeBSD-based FreeNAS operating system. Should the NFS shares be unmounted before suspension, and mounted after resume? Can this be done automatically?
I downloaded quicktime from the apple website because I am trying to get Itunes for fedora (If anyone knows another program that is functional with the IPOD please, let me know), I installed it with WINE, but the program is not responding well with my box. The program doesn't open, instead it black-out my computer screen and when I move the mouse over things, they then start to appear. Anyways...I tried uninstalling all of the files and folders that include the names "quicktime and qt"...then I tried re-installing QuickTime. Now I receive a reply that states "There is already a newer version of QuickTime installed on your computer." When I try