Bad news for Mint users who downloaded ISO files few days ago (20th Feb)…
Some dude found the way to replace the official Mint 17.3 Cinnamon ISOs with the cracked ISOs (with backdoor inside)
More details can be found here: http://blog.linuxmint.com/?p=2994
Also, as Clem announced, the forum database was compromised and you should change your password on all sensitive websites as soon as possible (in case you used the same password on other sites)
More details: http://blog.linuxmint.com/?p=3001
In case you’re using MySQL Workbench for creating dumps please keep in mind that version 6.3.5 has one annoying bug.
After update, the first time I tried do create dump, the complete process failed with the next error:
mysqldump: [ERROR] unknown variable 'delayed-insert=FALSE'
As I can see, this error occurs on various systems (Windows / MAC / Linux) and it was fixed once (6.1.x was also affected – LINK)
For now, you can only apply temporarily fix:
Open file (as root) wb_admin_export_options.py (located in /usr/lib/mysql-workbench/modules for Ubuntu/Mint/Debian distros)
Find the line
"delayed-insert":["Write INSERT DELAYED statements rather than..."
and insert # at the begin of this line (to comment it out)
Save file and restart Workbench. Check the Advanced option and note that this option is not available
Note: Windows users
For 32bit systems, wb_admin_export_options.py is located in C:\Program Files\MySQL\MySQL Workbench XXX\modules
For x64 systems, wb_admin_export_options.py is located in C:\Program Files (x86)\MySQL\MySQL Workbench XXX\modules)
The bug fix is easy to apply but it was announced months ago we’re still waiting for update… So shame…
Andama is an open source remote desktop software, with client side encryption and privacy in mind. The project is currently in funding phase so please help as much as you can.
Download current version
Laravel 5.x requires PHP version 5.5.9+. Also, in case you want to use database (sqlite or mysql), install Sqlite3, Mysql or PostgreSQL server.
Install composer with
curl -sS https://getcomposer.org/installer | php
sudo mv composer.phar /usr/local/bin/composer
Install Laravel (option 1)
composer create-project laravel/laravel laravel-test
Instal Laravel (option 2)
composer global require "laravel/installer=~1.1"
Add the following to .bashrc file
at the end of the file then in terminal type
and verify that $PATH variable contains the full path to laravel executable.
Then create new Laravel project with
php -S localhost:8888 -t public
and open http://localhost:8888 in your web browser
The Point-to-Point Tunneling Protocol (PPTP) is a method for implementing virtual private networks. Since it is marked as non secure and vulnerable, I don’t recommend it as a “final” VPN solution. The main reason for its popularity is probably the native MS Windows support (since win 95). Also, it can be easily implemented with Mikrotik RouterOS (like I said, use it for internal VPNs only).
To set up your CentOS box as a PPTP clients you’ll need the pptp package.
Open /etc/ppp/chap-secrets and add the next line (at the end). Also, replace the userName and password with the correct details:
Create profile file
and paste the next content (replace IP_OR_HOSTNAME with PPTP server IP or hostname)
pty "pptp IP_OR_HOSTNAME --nolaunchpppd"
save the file and test the connection with
ifconfig should return something like
ppp0 Link encap:Point-to-Point Protocol
inet addr:10.16.18.252 P-t-P:10.16.18.251 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1436 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:2192 (2.1 KiB) TX bytes:631 (631.0 b)
also in /var/log/messages you should see something like
Jul 20 10:58:50 mysrv pppd: pppd 2.4.5 started by root, uid 0
Jul 20 10:58:50 mysrv pppd: Using interface ppp0
Jul 20 10:58:50 mysrv pppd: Connect: ppp0 <--> /dev/pts/1
Jul 20 10:58:50 mysrv pptp: anon log[main:pptp.c:314]: The synchronous pptp option is NOT activated
Jul 20 10:58:50 mysrv pptp: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request'
Jul 20 10:58:50 mysrv pptp: anon log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply
Jul 20 10:58:50 mysrv pptp: anon log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established.
Jul 20 10:58:51 mysrv pptp: anon log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request'
Jul 20 10:58:51 mysrv pptp: anon log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply.
Jul 20 10:58:51 mysrv pptp: anon log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 716).
Jul 20 10:58:51 mysrv pppd: CHAP authentication succeeded
Jul 20 10:58:51 mysrv pppd: MPPE 128-bit stateless compression enabled
Jul 20 10:58:51 mysrv pppd: local IP address 10.16.18.252
Jul 20 10:58:51 mysrv pppd: remote IP address 10.16.18.251
Jul 20 10:59:51 mysrv pptp: anon log[logecho:pptp_ctrl.c:677]: Echo Reply received.
If you check your routes, you’ll probably notice that ppp0 connection is not used by any route(s). This is default behavior and you can easily switch/add default route with:
route add default dev ppp0
In my case, I don’t want to route the complete traffic (this VPN is just for management) so I’ll add only one static route
route add -net 192.168.120.0/24 dev ppp0
To start this connection on boot, add “pppd call myVPN” in rc.local.
According to this link , Google will abandon development and official support of the Android Developer Tools in Eclipse. Instead ADT, the main focus and interest will be on Android Studio. This applies specifically to the ADT plugin and Android Ant build system.
Projects from Eclipse can be easily migrated to Android Studio with just a few simple clicks.
For more information, please check the next link: Android Developers Blog
I found the next error message in the log
May 8 10:48:57 srv kernel: ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20130517/exfield-299)
May 8 10:48:57 srv kernel: ACPI Error: Method parse/execution failed [\_SB_.PMI0._PMM] (Node ffff88042949d960), AE_AML_BUFFER_LIMIT (20130517/psparse-536)
May 8 10:48:57 srv kernel: ACPI Exception: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20130517/power_meter-339)
The message is generated every 5 minutes when lm-sensors try to read the values from the power meter sensor(s). HP has ignored the spec for this method and the result is the error shown above.
The problem can be solved on two ways:
– you can ignore this message (it is safely to ignore)
– you can skip the power meter sensors (at least until someone fix this)
Since I already have the latest firmware, I can’t suggest the firmware update (at least for 310 gen8 server).
To reproduce the problem just find the file power1_average and try to read it
find /sys/devices/LNXSYSTM\:00/ |grep ACPI000D
In my case the file is located in /sys/devices/LNXSYSTM:00/device:00/ACPI000D:00/
Read the file
The result will be probably 0 and the error will be thrown in the log.
To solve the problem check the exact sensor which is affected with:
[root@srv log]# sensors
Adapter: ACPI interface
power1: 0.00 W (interval = 300.00 s)
As you can see above, the sensor is power_meter-acpi-0. Now disable the sensor by adding
at the end of the /etc/sensors3.conf file.
The reboot is recommended but it is not necessary.
Check the sensor again with
[root@srv log]# sensors
Adapter: ACPI interface
As you can see, the line “power1….” is missing and the log is empty.
If you’re a regular visitor, you’ll probably notice the new theme. I usually don’t change the things which works but since Google decided to penalize non mobile-friendly sites I had to change the theme.
Until I find the decent theme, …
If you’re trying to install CentOS 7 on HP server and you receive the error from the caption, don’t worry – you’re not alone. According to Google, there are about 48400 results related to this topic
The fix is still not available and according to HP, the problem is related to “Processor Power and Utilization Monitoring” function which should be disabled to fix this mess.
– All ProLiant Gen8 Servers
– ProLiant DL580 G7
– ProLiant BL620 G7
– ProLiant BL680 G7
How to disable “Processor Power and Utilization Monitoring”:
– enter BIOS (press F9 during boot)
– press CTRL+A (Service Option is hidden by default)
– select “Service Options” -> Processor Power and Utilization Monitoring -> Disable
Press F10 to save and exit and reboot the server.
More information can be found on the next links:
DL380 Gen9 is also affected with this problem. The solution remains the same (disable Processor Power and Utilization Monitoring)
Edit: 2016-03-31 (comment by Jimmy)
There really isn’t any fix needed. It is just an informational message. The system is reserving performance counters for system management and the kernel wants to own all the performance counters regardless. You can disable the ProLiant management features if you really want to stop the message. Other than printing the message during boot, there isn’t any negative impact on the system or performance.
The server which worked perfectly for years, after reboot decided to post the message:
Strike F1 key to continue, F2 for setup utility
The “fix” for this problem is to read carefully the posted messages shown during boot and to fix the problem. In my case, the problem was a faulty memory module which just lost a contact in the slot.