IT ROOM

I could see many people bug the developer with silly questions... I faced this issue on both Ubuntu, CentOS, and Fedora.  What I found is, the driver which Ubuntu, CentOS, or Fedora shipped is the latest one. There is no need of downloading and compiling the drivers again, without testing the installed driver with different antenna selections. In most cases re-enabling the kernel module with correct antenna selection would help.  (I think it will work in Redhat as well. But not tested.) Let me share my finding... To fix this you have to unload the current kernel modules and then insert them again with the new antenna selection... In my case, In Ubuntu the antenna was 2,  in centOS7 and Fedora, it was 1. So here are the steps (which I did). In UBUNTU (16.10, 17.04) ## Unload the current module ## sudo modprobe -rv rtl8723be ## Reload it with new option. ## sudo modprobe -v rtl8723be ant_sel=2 ## this step will help you to keep the same changes even after the reboot) ##

My backup team reported that the backups are failed. And on investigation I found /var/log/lastlog is very huge in size but file system usage is normal in "df" output.  And even "du" command also shows normal in size. I found this information from redhat. This file is what we call a sparse file. A sparse file is a file that contains unallocated blocks or "empty space", as it implies, it does not actually take up filesystem space. To test this theory, execute the following command: root@server1.nyc.us:/var/log # ls -l /var/log/lastlog -rw-r--r-- 1 root tty 459561084068 Jul 1 13:05 /var/log/lastlog root@server1.nyc.us:/var/log # du -sh /var/log/lastlog 23M /var/log/lastlog See the ls -l output, which shows huge size. The fix which they have suggested is to copy/move the file to some other place, because the copying will clear the unallocated blocks. But I found the copy is taking more time. So I decided to to clear the file after stopping th

VirtualBox-5.1 in not working in Fedora 25, Centos7 and Redhat Linux (RHEL) I installed Virtualbox-5.1 from the rpmfusion repository and I was unable to create Host-Only-Netwok adapter. When I tried to start create I got the below error. VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory Later I started researching what is this error and why it the device is not present. And I came to know that VirtualBox kernel modules were not started and that was causing the issue. I tried to start the service and it failed. (Unfortunately I don't have that output). I got the warding that kernel-core-devel is not installed on the system.  I tried to install it and that didn't worked since there was no kernel-core-devel package was not available in fedora repositories. Later I found some blogs where I got the actual fix. Here we have to uninstall the currently installed one from rpmfusion and we need to insta

How to kill the tty sessions in UNIX 1. First you have to check how many logins are present in server.  Use "w" command to list all the sessions . [root@testserver ~]# w  00:22:13 up 106 days, 22:41,  2 users ,  load average: 3.31, 1.53, 1.09 USER     TTY      FROM              LOGIN@   IDLE   JCPU   PCPU WHAT root     pts/15   master.world.com 00:22    1.00s  0.64s  0.61s w root     pts/18    10.47.18.111      09Mar14  36days  0.01s  0.01s -bash Total 2 users are logged in. See there is a session from the IP 10.47.18.111 is idle for last 36 days.  And I want to end this session.  For that we have to note down the tty id which is used for this Login. See here it is  pts/18 .  2.  Now you have to find out what is the process id of this particular tty session - pts/18 . "ps -ft" is using for this purpose.  [root@testserver ~]# ps -ft pts/18 UID        PID  PPID  C STIME TTY          TIME CMD root      9886  9882  0 Mar09 pts/18   00:00:00 -bash 3. N

Zimbra Collaboration Server 8 is susceptible to the OpenSSL Heartbleed bug:   Specifically, nginx, postfix and OpenLDAP all link directly to OpenSSL shipped in ZCS8. Other components in the ZCS package also link to the openssl libraries, but the above three are the potentially Internet-facing services that would be attackable. All versions of ZCS8 as released today are vulnerable. ZCS7 is not vulnerable because it uses OpenSSL 1.0.0, which is not vulnerable. Only OpenSSL 1.0.1 and later are reported as being vulnerable. Zimbra has produced an OpenSSL patch for versions 8.0.3 to 8.0.7. If you are running a version prior to 8.0.3, your server is susceptible to other critical security vulnerabilities [reference: https://www.zimbra.com/forums/announ...-84547-a.html] , so you would please need to upgrade to a secure version first, then run this patch. The patch is located here: http://files.zimbra.com/downloads/se...ssl-updater.sh The patch downloads the correct and

[SOLVED] Hi Guys , Some times back I have faced some problem in one my squid proxy server. My squid service was killed and was failed to start the service.  # service squid start Starting squid: ....................                       [FAILED] There was no visible error on that screen. It simply returned the status is failed. Then I check the log file of system. There was an error " exited due to signal 25 ". Jul 27 12:48:46 PRXY squid[14372]: Squid Parent: child process 14375 started Jul 27 12:48:46 PRXY squid[14372]: Squid Parent: child process 14375 exited due to signal 25 Jul 27 12:48:49 PRXY squid[14372]: Squid Parent: child process 14381 started Jul 27 12:48:50 PRXY squid[14372]: Squid Parent: child process 14381 exited due to signal 25 Jul 27 12:48:53 PRXY squid[14372]: Squid Parent: child process 14387 started Jul 27 12:48:53 PRXY squid[14372]: Squid Parent: child process 14387 exited due to signal 25 Jul 27 12:48:56 PRXY squid[14372]: