Dear All, I have configured Cluster Suite with 2 servers Server 1 : 192.168.13.110 IP Address and hostname is primary Server 2 : 192.168.13.179 IP Address and hostname is secondary Floating : 192.168.13.83 IP Address (Assumed by currently active server)
I have configured Ethernet Channel Bonding in Each Cluster Nodes and Channel Bonding Configuration Details are 1) Created bonding devices in "/etc/modprobe.conf" file alias bond0 bonding options bonding miimon=100 mode=1 2) Edit the "/etc/sysconfig/network-scripts/ifcfg-eth0 and ifcfg-eth1" configuration DEVICE=eth0 USERCTL= no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none
DEVICE=eth1 USERCTL= no ONBOOT=yes MASTER=bond0 SLAVE=yes BOOTPROTO=none 3) Created a network script for the bonding device is "/etc/sysconfig/network-scripts/ifcfg-bond0" DEVICE=bond0 USERCTL=no ONBOOT=yes NETMASK=255.255.255.0 GATEWAY=192.168.13.1 IPADDR=192.168.13.110 4) Reboot the system for the changes to take effect.
After i am rebooted both the server then cluster node becomes simplex and Services are started on both the nodes The cluster output in primary node
Member Status: Quorate
Member Name Status ----------- --------- primary Online, Local, rgmanager secondary Offline
Service Name Owner (Last) State ------------ ------------ -------- Service primary started
The cluster output in secondary node
Member Status: Quorate
Member Name Status ----------- --------- primary Offline secondary Online, Local, rgmanager
Service Name Owner (Last) State ------------ -------------- -------- Service secondary started
Before Ethernet Channel Bonding cluster services are active in one node and other nodes acts as passive node. But after Ethernet Channel Bonding cluster services are active on both the nodes
I don't know what is the problem and is their any configuration is required in cluster configuration file and cman is working only with eth0 interface
Can some one throw light on this peculiar problem
Regards -S.Balaji
Here is the original cron.daily for webalizer.
#if [ -s /var/log/httpd/access_log ]; then exec /usr/bin/webalizer -Q; Fi
I want to add two more for the virtual domains.
I tried adding these
if [ -s /var/log/httpd/mysite1_access_log ]; then exec /usr/bin/webalizer -Qc /etc/webalizer/mysite1.conf; fi if [ -s /var/log/httpd/mysite2_access_log ]; then exec /usr/bin/webalizer -Qc /etc/webalizer/mysite2.conf; Fi
If I do not add the fi after each, the file gets an error when I run /etc/cron.daily/00webalizer
I added the -c and the conf file, but I feel that I am missing the correct syntax.
Or am I supposed to make a new file for each.
What worked for the cron...but not doing the original one is this...
for i in /etc/webalizer/*.conf; do webalizer -Qc $i; done
I guess a second one needs to be made for the main one...or maybe another line.
But this worked.
Hi,
On Fri, Sep 12, 2008 at 01:38, Bob Hoffman bob@bobhoffman.com wrote:
if [ -s /var/log/httpd/mysite1_access_log ]; then exec /usr/bin/webalizer -Qc /etc/webalizer/mysite1.conf; fi if [ -s /var/log/httpd/mysite2_access_log ]; then exec /usr/bin/webalizer -Qc /etc/webalizer/mysite2.conf; Fi
You have to remove the "exec" from the command lines. "exec" means the program that will run will replace the script, so no command after that one will execute on the script.
If I do not add the fi after each, the file gets an error when I run /etc/cron.daily/00webalizer
Yes, you must keep the "fi"s, and I believe they should be lowercase.
HTH, Filipe
Finsihing my server set up.. Yum-updatesd
This is on, via the chkconfig and seems to run a lot.
TO DO: auto update YUM for the computer once a day. Files: /etc/yum/yum-updatesd.conf Extra: send a mail or add to log file
This is the centos original file and my suggested changes. If anyone uses this, do you have something similar?
[main] # how often to check for new updates (in seconds) run_interval = 3600 (gonna change to 86400 for 24 hours)
# how often to allow checking on request (in seconds) updaterefresh = 600 (leave as is)
# how to send notifications (valid: dbus, email, syslog) emit_via = dbus (change to email, defaults to root I believe)
# should we listen via dbus to give out update information/check for # new updates dbus_listener = yes (assume no?)
# automatically install updates do_update = no (change to yes)
# automatically download updates do_download = no (change to yes)
# automatically download deps of updates do_download_deps = no (change to yes)
I am not sure about the dbus listener. The documentation, yum wiki, or the man pages were not telling me anything.
Thanks
on 9-12-2008 2:15 PM Bob Hoffman spake the following:
Finsihing my server set up.. Yum-updatesd
This is on, via the chkconfig and seems to run a lot.
TO DO: auto update YUM for the computer once a day. Files: /etc/yum/yum-updatesd.conf Extra: send a mail or add to log file
This is the centos original file and my suggested changes. If anyone uses this, do you have something similar?
I don't run it on critical servers. I have had too many updates that needed to have manual intervention to get the server running again. Most were trivial to fix, but it still took someone being there to fix it.
On 12 Sep 2008, at 14:47, Scott Silva wrote:
If anyone uses this, do you have something similar?
I don't run it on critical servers. I have had too many updates that needed to have manual intervention to get the server running again. Most were trivial to fix, but it still took someone being there to fix it.
Here is how I have it configured for critical systems. Works great, Centos 5.2, x86. Email notices can get annoying if you're not around a terminal for several hours/days, as it continues to notify you each hour it checks and finds an update.
[main] # how often to check for new updates (in seconds) run_interval = 3600 # how often to allow checking on request (in seconds) updaterefresh = 600
# how to send notifications (valid: dbus, email, syslog) emit_via = email # should we listen via dbus to give out update information/check for # new updates dbus_listener = yes
# automatically install updates do_update = no # automatically download updates do_download = no # automatically download deps of updates do_download_deps = no
# who to notify email_to = root@localhost email_from = yum@localhost
Jeremiah
On Fri, 2008-09-12 at 17:15 -0400, Bob Hoffman wrote:
Finsihing my server set up.. Yum-updatesd
This is on, via the chkconfig and seems to run a lot.
TO DO: auto update YUM for the computer once a day. Files: /etc/yum/yum-updatesd.conf Extra: send a mail or add to log file
This is the centos original file and my suggested changes. If anyone uses this, do you have something similar?
[main] # how often to check for new updates (in seconds) run_interval = 3600 (gonna change to 86400 for 24 hours)
# how often to allow checking on request (in seconds) updaterefresh = 600 (leave as is)
# how to send notifications (valid: dbus, email, syslog) emit_via = dbus (change to email, defaults to root I believe)
# should we listen via dbus to give out update information/check for # new updates dbus_listener = yes (assume no?)
# automatically install updates do_update = no (change to yes)
# automatically download updates do_download = no (change to yes)
# automatically download deps of updates do_download_deps = no (change to yes)
I am not sure about the dbus listener. The documentation, yum wiki, or the man pages were not telling me anything.
---- yum-updatesd...I never got it to work in Fedora 7 but it does work in Fedora 8. I recall a discussion a few months ago that it didn't actually work in CentOS-5 but perhaps the 5.2 update actually made it work...I simply don't know.
below is my configuration of /etc/yum/yum-updatesd.conf that works on Fedora 8
# cat /etc/yum/yum-updatesd.conf [main] # how often to check for new updates (in seconds) run_interval = 3600 # how often to allow checking on request (in seconds) updaterefresh = 600
# how to send notifications (valid: dbus, email, syslog) emit_via = syslog
# automatically install updates do_update = yes # automatically download updates do_download = yes # automatically download deps of updates do_download_deps = yes
(I never tried e-mail notifications)
Craig
I read somewhere, that one of the issues was choking on sending emails..due to sending to nobody account. I guess I will have to wait and look for errors. I do know that it was always on and had never told me there was an update available when logging in as root.
below is my configuration of /etc/yum/yum-updatesd.conf that works on Fedora 8
# cat /etc/yum/yum-updatesd.conf [main] # how often to check for new updates (in seconds) run_interval = 3600 # how often to allow checking on request (in seconds) updaterefresh = 600
# how to send notifications (valid: dbus, email, syslog) emit_via = syslog
# automatically install updates do_update = yes # automatically download updates do_download = yes # automatically download deps of updates do_download_deps = yes
(I never tried e-mail notifications)
Craig
os
Bob Hoffman wrote:
This is on, via the chkconfig and seems to run a lot. TO DO: auto update YUM for the computer once a day. Files: /etc/yum/yum-updatesd.conf Extra: send a mail or add to log file
Isn't that overkill for an enterprise distro? Subscribing to the relevant mailing list should help shouldn't it? Not even considering the potential load on the CentOS servers, shouldn't an admin test updates without letting yum auto-update? Updates do have issues too.
Thanks, Josh.
This is on, via the chkconfig and seems to run a lot. TO DO: auto update YUM for the computer once a day. Files: /etc/yum/yum-updatesd.conf Extra: send a mail or add to log file
Isn't that overkill for an enterprise distro? Subscribing to the relevant mailing list should help shouldn't it? Not even considering the potential load on the CentOS servers, shouldn't an admin test updates without letting yum auto-update? Updates do have issues too.
The default setting is every hour. Checking for an update at least once a day is not bad as a bug fix can come in at anytime. I would think that is very important for the server.
As for updates with issues, so far none, but I guess they will happen. I slimmed down my system, and continue to do so, in the hopes that the less stuff running, the less problems updating.
So far though, no problems with any update so far.
Bob Hoffman wrote:
The default setting is every hour. Checking for an update at least once a day is not bad as a bug fix can come in at anytime. I would think that is very important for the server.
Is CentOS your first introduction to Linux? You may need to cut your teeth upstream on Fedora (a cutting edge product) as it changes frequently and has tons of updates. With an Enterprise distro the aim is stability to run mission critical servers.
With the latest and greatest distro (Fedora), the aim is to roll out tons of updates and have you test them out.
Thanks, Josh.
Update
At 1:40 this morning, server time, I received an email from the server...the text is below
======================= Hi, This is the automatic update system on server.creativeprogramdesigners.com.
The system successfully installed/updated 5 packages.
Packages installed or updated:
libxml2 libxml2 libxml2-python sos tzdata
Thank You, Your Computer =========================
So the settings of having yum-updatesd to chkconfig on worked. The settings in the file that I did for once a day and stuff...appears it all worked.
Awesome. Centos 5.x, fully updated.
-
Balaji -
Bob Hoffman -
Craig White -
Filipe Brandenburger -
Jeremiah Heller -
Josh Donovan -
Scott Silva