rev.dennis

Do you have a mouse pointer that moves back and forth or jumps around or bounces on your Debian based Linux system? This includes Ubuntu and Linux Mint systems as well as many others based on the Debian core. Here are some fixes that you could try and see if they resolve the issue for you. TRY #1 sudo nano /etc/X11/xorg.conf and then adding Option "HWCursor" "false" to the Device section; TRY #2 sudo nano /etc/X11/xorg.conf and then find this section Section "InputDevice" Identifier "Synaptics Touchpad" and add Option "SHMConfig" "on", after which you save the file and then add syndaemon -i 3 -d -t -k to your startup programs (System -> Preferences -> Sessions -> Startup Programs) where the usage for syndaemon is: Usage: syndaemon -i How many seconds to wait after the last key press before enabling the touchpad. (default is 2.0s) -m How many milli-seconds to wait until next poll. (default is 200ms) -d Start as a daemon, ie in the background. -p Create a pid file with the specified name. -t Only disable tapping and scrolling, not mouse movements. -k Ignore modifier keys when monitoring keyboard activity. -K Like -k but also ignore Modifier+Key combos. -S Use SHMConfig even if input device properties are available. TRY #3 Install an application that automatically disables the touchpad on your laptop while you are typing and then re-enables it after a short period of time (that you set). sudo apt-get install touchfreeze NOTE: Don't forget to add it to the Startup Programs like the other Try's noted above.

Do you have a mouse pointer that moves back and forth or jumps around or bounces on your Debian based Linux system? This includes Ubuntu and Linux Mint systems as well as many others based on the Debian core. Here are some fixes that you could try and see if they resolve the issue for you. TRY #1 sudo nano /etc/X11/xorg.conf and then adding Option "HWCursor" "false" to the Device section; TRY #2 sudo nano /etc/X11/xorg.conf and then find this section Section "InputDevice" Identifier "Synaptics Touchpad" and add Option "SHMConfig" "on", after which you save the file and then add syndaemon -i 3 -d -t -k to your startup programs (System -> Preferences -> Sessions -> Startup Programs) where the usage for syndaemon is: Usage: syndaemon -i How many seconds to wait after the last key press before enabling the touchpad. (default is 2.0s) -m How many milli-seconds to wait until next poll. (default is 200ms) -d Start as a daemon, ie in the background. -p Create a pid file with the specified name. -t Only disable tapping and scrolling, not mouse movements. -k Ignore modifier keys when monitoring keyboard activity. -K Like -k but also ignore Modifier+Key combos. -S Use SHMConfig even if input device properties are available. TRY #3 Install an application that automatically disables the touchpad on your laptop while you are typing and then re-enables it after a short period of time (that you set). sudo apt-get install touchfreeze NOTE: Don't forget to add it to the Startup Programs like the other Try's noted above.

Installing Smokeping is relatively simple. Just issue this command as root. sudo yum -y install smokeping and It will install smokeping along with all other tools and dependencies it requires. NOTE: selinux is the Problem. By default its enabled in Fedora installation. Disable it by editing sudo nano /etc/selinux/config and change the enable to disable as following. SELINUX=disable (Restart your nix box.) After installation completes, You can access it via http://yourIPaddress/cgi-bin/sm.cgi NOTE: If you get Access Denied: You dont have permission to access this Folder error, edit the following line. nano /etc/httpd/conf.d/smokeping.conf and remove all lines in this file , and paste the following. order deny,allow allow from 127.0.0.1 allow from all order deny,allow allow from 127.0.0.1 allow from all ScriptAlias /smokeping/sm.cgi /usr/share/smokeping/cgi/smokeping.cgi ScriptAlias /smokeping/tr.cgi /usr/share/smokeping/cgi/tr.cgi Alias /smokeping/images /var/lib/smokeping/images Alias /smokeping /usr/share/smokeping/htdocs Save & exit. Now restart apache web server by service httpd restart Now try to access the smokeping cgi, it will open properly. http://yourIPaddress/cgi-bin/sm.cgi Now Its time to add your target in Smokeping for monitoring. The default location for the Smokeping config file is /etc/smokeping/config, Now just for example, we will edit this file. nano /etc/smokeping/config Remove all the lines in it and paste the following lines *** General *** owner = Syed Jahanzaib contact = [email protected] mailhost = smtp.ptcl.com sendmail = /usr/sbin/sendmail imgcache = /var/lib/smokeping/images imgurl = /smokeping/images datadir = /var/lib/smokeping/rrd piddir = /var/run/smokeping cgiurl = http://localhost/smokeping/smokeping.cgi smokemail = /etc/smokeping/smokemail tmail = /etc/smokeping/tmail syslogfacility = local0 *** Alerts *** to = root@localhost from = root@localhost +someloss type = loss pattern = >0%,*12*,>0%,*12*,>0% comment = loss 3 times in a row *** Database *** step = 300 pings = 20 # consfn mrhb steps total AVERAGE 0.5 1 1008 AVERAGE 0.5 12 4320 MIN 0.5 12 4320 MAX 0.5 12 4320 AVERAGE 0.5 144 720 MAX 0.5 144 720 MIN 0.5 144 720 *** Presentation *** template = /etc/smokeping/basepage.html + charts menu = Charts title = The most interesting destinations ++ stddev sorter = StdDev(entries=>4) title = Top Standard Deviation menu = Std Deviation format = Standard Deviation %f ++ max sorter = Max(entries=>5) title = Top Max Roundtrip Time menu = by Max format = Max Roundtrip Time %f seconds ++ loss sorter = Loss(entries=>5) title = Top Packet Loss menu = Loss format = Packets Lost %f ++ median sorter = Median(entries=>5) title = Top Median Roundtrip Time menu = by Median format = Median RTT %f seconds + overview width = 600 height = 50 range = 10h + detail width = 600 height = 200 unison_tolerance = 2 "Last 3 Hours" 3h "Last 30 Hours" 30h "Last 10 Days" 10d "Last 400 Days" 400d *** Probes *** + FPing binary = /usr/sbin/fping *** Slaves *** secrets=/etc/smokeping/smokeping_secrets +boomer display_name=boomer color=0000ff +slave2 display_name=another color=00ff00 *** Targets *** probe = FPing menu = Top title = Network Latency Grapher remark = Welcome to the SmokePing website of GLASSLINE (Pvt) Ltd. Here you will learn all about the latency of our network. This page is maintained by Glassline. (Pvt) ltd . Support Email: [email protected] Web: https://aacable.wordpress.com ### YOU CAN CHANGE THE FOLLOWING ACCORDING TO YOUR NETWORK ### + Ping menu = WAN Connectivity title = WAS Side Network ++ yahoo menu = yahoo title = yahoo ping report host = yahoo.com ++ google menu = google title = Google ping report host = google.com ### YOU CAN CHANGE FOLLOWING ACCORDING TO YOUR NETWORK ### + Ping2 menu = LAN Connectivity title = LAN Side Network ++ Mikrotik menu = Mikrotik title = Mikrotik PPP ping report host = 10.10.0.1 ++ Proxy menu = Proxy title = Proxy Server ping report host = 10.10.0.2 ++ Billing menu = Billing title = Radius billing Server ping report host = 10.10.0.2 Now restart smokeping process by /etc/init.d/smokeping restart Default update time for all ping probes are 5 Minutes. Try accessing the main smokeping page after 5-10 minutes so it can create necessary RRD for targets and update its graphs. http://yourIPaddress/cgi-bin/sm.cgi Click on LAN connectivity to open graphs. Click on WAN Connectivity Click on the Yahoo Ping Graph showing on Right to get more detailed graph report. To get more detailed view, click on Last 3 hours graphs, It will open this graph in NAVIGATOR mode. Now here you can select any specific area to zoom to troubleshoot at exact which time the latency problems occurs. For example in the following screenshot you can see the blue dots which shows that ping timeout occurs at specific time. PULL DATA FROM SPECIFIC TIME A client complained that the internet worked very slow in the morning at 10:30am. So you can pull data from smokeping graph to validate the complain or to troubleshoot what exactly happened at 10:30am As you can see the blue dots showed that the ping breaks occured in the specific timings. There are so many interesting things you can do with SMOKE-PING. For some more examples , please visit the author web site @ http://oss.oetiker.ch/smokeping/index.en.html

Installing Smokeping is relatively simple. Just issue this command as root. sudo yum -y install smokeping and It will install smokeping along with all other tools and dependencies it requires. NOTE: selinux is the Problem. By default its enabled in Fedora installation. Disable it by editing sudo nano /etc/selinux/config and change the enable to disable as following. SELINUX=disable (Restart your nix box.) After installation completes, You can access it via http://yourIPaddress/cgi-bin/sm.cgi NOTE: If you get Access Denied: You dont have permission to access this Folder error, edit the following line. nano /etc/httpd/conf.d/smokeping.conf and remove all lines in this file , and paste the following. order deny,allow allow from 127.0.0.1 allow from all order deny,allow allow from 127.0.0.1 allow from all ScriptAlias /smokeping/sm.cgi /usr/share/smokeping/cgi/smokeping.cgi ScriptAlias /smokeping/tr.cgi /usr/share/smokeping/cgi/tr.cgi Alias /smokeping/images /var/lib/smokeping/images Alias /smokeping /usr/share/smokeping/htdocs Save & exit. Now restart apache web server by service httpd restart Now try to access the smokeping cgi, it will open properly. http://yourIPaddress/cgi-bin/sm.cgi Now Its time to add your target in Smokeping for monitoring. The default location for the Smokeping config file is /etc/smokeping/config, Now just for example, we will edit this file. nano /etc/smokeping/config Remove all the lines in it and paste the following lines *** General *** owner = Syed Jahanzaib contact = [email protected] mailhost = smtp.ptcl.com sendmail = /usr/sbin/sendmail imgcache = /var/lib/smokeping/images imgurl = /smokeping/images datadir = /var/lib/smokeping/rrd piddir = /var/run/smokeping cgiurl = http://localhost/smokeping/smokeping.cgi smokemail = /etc/smokeping/smokemail tmail = /etc/smokeping/tmail syslogfacility = local0 *** Alerts *** to = root@localhost from = root@localhost +someloss type = loss pattern = >0%,*12*,>0%,*12*,>0% comment = loss 3 times in a row *** Database *** step = 300 pings = 20 # consfn mrhb steps total AVERAGE 0.5 1 1008 AVERAGE 0.5 12 4320 MIN 0.5 12 4320 MAX 0.5 12 4320 AVERAGE 0.5 144 720 MAX 0.5 144 720 MIN 0.5 144 720 *** Presentation *** template = /etc/smokeping/basepage.html + charts menu = Charts title = The most interesting destinations ++ stddev sorter = StdDev(entries=>4) title = Top Standard Deviation menu = Std Deviation format = Standard Deviation %f ++ max sorter = Max(entries=>5) title = Top Max Roundtrip Time menu = by Max format = Max Roundtrip Time %f seconds ++ loss sorter = Loss(entries=>5) title = Top Packet Loss menu = Loss format = Packets Lost %f ++ median sorter = Median(entries=>5) title = Top Median Roundtrip Time menu = by Median format = Median RTT %f seconds + overview width = 600 height = 50 range = 10h + detail width = 600 height = 200 unison_tolerance = 2 "Last 3 Hours" 3h "Last 30 Hours" 30h "Last 10 Days" 10d "Last 400 Days" 400d *** Probes *** + FPing binary = /usr/sbin/fping *** Slaves *** secrets=/etc/smokeping/smokeping_secrets +boomer display_name=boomer color=0000ff +slave2 display_name=another color=00ff00 *** Targets *** probe = FPing menu = Top title = Network Latency Grapher remark = Welcome to the SmokePing website of GLASSLINE (Pvt) Ltd. Here you will learn all about the latency of our network. This page is maintained by Glassline. (Pvt) ltd . Support Email: [email protected] Web: https://aacable.wordpress.com ### YOU CAN CHANGE THE FOLLOWING ACCORDING TO YOUR NETWORK ### + Ping menu = WAN Connectivity title = WAS Side Network ++ yahoo menu = yahoo title = yahoo ping report host = yahoo.com ++ google menu = google title = Google ping report host = google.com ### YOU CAN CHANGE FOLLOWING ACCORDING TO YOUR NETWORK ### + Ping2 menu = LAN Connectivity title = LAN Side Network ++ Mikrotik menu = Mikrotik title = Mikrotik PPP ping report host = 10.10.0.1 ++ Proxy menu = Proxy title = Proxy Server ping report host = 10.10.0.2 ++ Billing menu = Billing title = Radius billing Server ping report host = 10.10.0.2 Now restart smokeping process by /etc/init.d/smokeping restart Default update time for all ping probes are 5 Minutes. Try accessing the main smokeping page after 5-10 minutes so it can create necessary RRD for targets and update its graphs. http://yourIPaddress/cgi-bin/sm.cgi Click on LAN connectivity to open graphs. Click on WAN Connectivity Click on the Yahoo Ping Graph showing on Right to get more detailed graph report. To get more detailed view, click on Last 3 hours graphs, It will open this graph in NAVIGATOR mode. Now here you can select any specific area to zoom to troubleshoot at exact which time the latency problems occurs. For example in the following screenshot you can see the blue dots which shows that ping timeout occurs at specific time. PULL DATA FROM SPECIFIC TIME A client complained that the internet worked very slow in the morning at 10:30am. So you can pull data from smokeping graph to validate the complain or to troubleshoot what exactly happened at 10:30am As you can see the blue dots showed that the ping breaks occured in the specific timings. There are so many interesting things you can do with SMOKE-PING. For some more examples , please visit the author web site @ http://oss.oetiker.ch/smokeping/index.en.html

Okay, my experience on exporting and importing mySQL Database Exporting (Pretty Easy) [root@ipsetest ~]# mysqldump -u root -p oaipse > oaipse.sql Importing (not too bad but learned a couple of things) [root@ipseweb ~]# mysql -u root -p oaipse < oaipse.sql Enter password: ERROR 1153 (08S01) at line 732: Got a packet bigger than 'max_allowed_packet' bytes To fix ERROR 1153 perform the following otherwise your database imported successfully. [root@ipseweb ~]# mysql -u root -p Enter password: mysql> set global net_buffer_length=1000000; mysql> set global max_allowed_packet=1000000000; mysql> exit Rerun the import command as noted above before error Verify your database imported [root@ipseweb ~]# mysqlshow -u root -p

Okay, my experience on exporting and importing mySQL Database Exporting (Pretty Easy) [root@ipsetest ~]# mysqldump -u root -p oaipse > oaipse.sql Importing (not too bad but learned a couple of things) [root@ipseweb ~]# mysql -u root -p oaipse < oaipse.sql Enter password: ERROR 1153 (08S01) at line 732: Got a packet bigger than 'max_allowed_packet' bytes To fix ERROR 1153 perform the following otherwise your database imported successfully. [root@ipseweb ~]# mysql -u root -p Enter password: mysql> set global net_buffer_length=1000000; mysql> set global max_allowed_packet=1000000000; mysql> exit Rerun the import command as noted above before error Verify your database imported [root@ipseweb ~]# mysqlshow -u root -p

Also known as NetSaint until they got pulled into court from Agios because apparantly they mean similar things so they changed from NetSaint to Nagios which pretty much stands for "Nagios Ain't Gonna Insist On Sainthood" Installation of Nagios is pretty straight forward and can be installed on Fedora, openSUSE or Ubuntu. They have quick start guides for each. You can also take advantage of a free compiled installation from iso or rpm from FAN (Fully Automated Nagios installation). The purpose of FAN is to provide a quick and easy installation which includes the most used tools in the Nagios community. The FAN CD-ROM is ISO-certified, it is thus very easy to install. A large number of tools are also being distributed, which makes the implementation of an efficient monitoring platform much easier. It includes CentOS which is a Fedora/RedHat based Linux install. Once you get Nagios installed, comes the somewhat confusing part.. at least at the beginning, the cfg files. A breakdown of some important .cfg files you need to be aware of /etc/nagios/nagios.cfg For the most part, I just point the cfg file to monitor folders for .cfg files and load them into nagios. Now for this to work, your .cfg files must not have any errors which I'll go over later. So to point to a directory search for cfg_dir= and you should get down to an area of the nagios.cfg file where you can point to a directory. Since I'm primarily monitoring servers my line looks like this cfg_dir=/etc/nagios/objects/servers /etc/nagios/objects/hostgroups.cfg <-- make sure this is listed in nagios.cfg This will group your hosts into meaningful hostgroups. Maybe it would be helpful to group all your DNS Servers together, DHCP Servers, Web Servers, etc.. /etc/nagios/objects/services.cfg <-- make sure this is listed in nagios.cfg This tells nagios what services you want to monitor on your hosts and you can assign them to your hostgroups so maybe you are only monitoring web services on your Web Servers, etc.. Now troubleshooting why nagios won't start can be a bit of a pain if you don't know how to find out why won't nagios start. I went through the logs and just couldn't figure out why it would fail the pre-check until I learned this. Instead of starting nagios the typical way /etc/init.d/nagios start, start nagios this way, /usr/bin/nagios -v /etc/nagios/nagios.cfg then you will be displayed why it's not starting.

Also known as NetSaint until they got pulled into court from Agios because apparantly they mean similar things so they changed from NetSaint to Nagios which pretty much stands for "Nagios Ain't Gonna Insist On Sainthood" Installation of Nagios is pretty straight forward and can be installed on Fedora, openSUSE or Ubuntu. They have quick start guides for each. You can also take advantage of a free compiled installation from iso or rpm from FAN (Fully Automated Nagios installation). The purpose of FAN is to provide a quick and easy installation which includes the most used tools in the Nagios community. The FAN CD-ROM is ISO-certified, it is thus very easy to install. A large number of tools are also being distributed, which makes the implementation of an efficient monitoring platform much easier. It includes CentOS which is a Fedora/RedHat based Linux install. Once you get Nagios installed, comes the somewhat confusing part.. at least at the beginning, the cfg files. A breakdown of some important .cfg files you need to be aware of /etc/nagios/nagios.cfg For the most part, I just point the cfg file to monitor folders for .cfg files and load them into nagios. Now for this to work, your .cfg files must not have any errors which I'll go over later. So to point to a directory search for cfg_dir= and you should get down to an area of the nagios.cfg file where you can point to a directory. Since I'm primarily monitoring servers my line looks like this cfg_dir=/etc/nagios/objects/servers /etc/nagios/objects/hostgroups.cfg <-- make sure this is listed in nagios.cfg This will group your hosts into meaningful hostgroups. Maybe it would be helpful to group all your DNS Servers together, DHCP Servers, Web Servers, etc.. /etc/nagios/objects/services.cfg <-- make sure this is listed in nagios.cfg This tells nagios what services you want to monitor on your hosts and you can assign them to your hostgroups so maybe you are only monitoring web services on your Web Servers, etc.. Now troubleshooting why nagios won't start can be a bit of a pain if you don't know how to find out why won't nagios start. I went through the logs and just couldn't figure out why it would fail the pre-check until I learned this. Instead of starting nagios the typical way /etc/init.d/nagios start, start nagios this way, /usr/bin/nagios -v /etc/nagios/nagios.cfg then you will be displayed why it's not starting.

When you are having issues connecting to a site all of a sudden, more than likely the site has performed an update and your browser is using its local cache trying to connect so you need to clear it out. This way your browser will download the updated information. Internet Explorer Internet Options - General Tab - Under Browsing History click Delete.. - select everything but Download History, Passwords and ActiveX Filtering aren't necessary if you don't want), - Click Delete Firefox Tools - Options - Privacy - clear your recent history Time range to clear: Everyting Details: Select what you want (more is better but mainly cache and cookies is a must) Click Clear Now

When you are having issues connecting to a site all of a sudden, more than likely the site has performed an update and your browser is using its local cache trying to connect so you need to clear it out. This way your browser will download the updated information. Internet Explorer Internet Options - General Tab - Under Browsing History click Delete.. - select everything but Download History, Passwords and ActiveX Filtering aren't necessary if you don't want), - Click Delete Firefox Tools - Options - Privacy - clear your recent history Time range to clear: Everyting Details: Select what you want (more is better but mainly cache and cookies is a must) Click Clear Now

Did the open atrium updates that it said to do and now when I try and search on the site it fails and spits out the following error SQLSTATE: Base table or view not found: 1146 Table 'oaipse.search_api_db_database_node_index_body_summary' doesn't exist

Did the open atrium updates that it said to do and now when I try and search on the site it fails and spits out the following error SQLSTATE: Base table or view not found: 1146 Table 'oaipse.search_api_db_database_node_index_body_summary' doesn't exist

New site, in the discussion (forum) section upon clicking on the + (plus) button to add a topic I receive the following error

New site, in the discussion (forum) section upon clicking on the + (plus) button to add a topic I receive the following error

I attempted to "customize this page" and save a change to the layout on a space and as I click Save I get the following Google Chrome error: I tried to resave and I get

I attempted to "customize this page" and save a change to the layout on a space and as I click Save I get the following Google Chrome error: I tried to resave and I get

I need to move from MAMP PRO installation on my awesome MacBook to a Linux (Redhat) server running webmin (no myphpadmin)... I know three things need to happen overall 1. put site into maintenace mode 2. export / then import mySQL database 3. Copy over files Hopefully that works.... let's find out.

I need to move from MAMP PRO installation on my awesome MacBook to a Linux (Redhat) server running webmin (no myphpadmin)... I know three things need to happen overall 1. put site into maintenace mode 2. export / then import mySQL database 3. Copy over files Hopefully that works.... let's find out.

An error that happens everywhere on the site and will sometimes goaway if I reload the page. Again, having issues finding anywhere that provides some free support for Open Atrium. Of course phase2 will provide pay support but I'm not making any money on this job.

An error that happens everywhere on the site and will sometimes goaway if I reload the page. Again, having issues finding anywhere that provides some free support for Open Atrium. Of course phase2 will provide pay support but I'm not making any money on this job.

Another issue I'm searching for results for since I'm having a heck of a time finding any support for Open Atrium

Another issue I'm searching for results for since I'm having a heck of a time finding any support for Open Atrium

Not as easy as I thought it would be but I am very much new to Drupal 7.. pretty much built all my websites on Joomla. I'm putting this here as a learning lession... I installed Open Atrium on Drupal 7 on my MAMP Pro install and a few items that would of been nice to know before I started this several day process. MAMP PRO users, you must point your Mac OS X PATH statement to use the PHP included in MAMP PRO since OS X comes with its own version it messes with things. It's not difficult

Not as easy as I thought it would be but I am very much new to Drupal 7.. pretty much built all my websites on Joomla. I'm putting this here as a learning lession... I installed Open Atrium on Drupal 7 on my MAMP Pro install and a few items that would of been nice to know before I started this several day process. MAMP PRO users, you must point your Mac OS X PATH statement to use the PHP included in MAMP PRO since OS X comes with its own version it messes with things. It's not difficult

One of the most popular internet browsers out there today is Firefox with Chrome being second and Safari next and Internet Explorer consistently falling to last place because of its proprietary features and Microsoft coding. Why is Firefox, Chrome and Safari doing so well. They are built to run on any website not just those websites created with Microsoft FrontPage. Also Firefox and Chrome work on most operating system platforms (Windows, Mac, Linux)... IE only works on windows. So some simple things to do to troubleshoot Firefox. 1. Reset Firefox by typing in the address bar.. about:config 2. Click Reset Firefox Now maybe when you launch firefox it crashes... try and launch it via safe-mode Windows: "C:Program FilesMozilla Firefoxfirefox.exe" -safe-mode Mac: Hold the Option key while launching Firefox Linux: from command line firefox -safe-mode