CUPS Printer cancel all pending jobs

[[email protected] ~]# lpq
SPDDCNPH09 is ready
no entries
[[email protected] ~]# lpstat -o
SPLDPHCA02-1994129 applprod 2048 Wed 18 Jan 2017 11:24:54 AM GST
DPDDCNPH03-1994219 applprod 2048 Wed 18 Jan 2017 11:28:03 AM GST
NWADCNPH20-1994345 applprod 2048 Wed 18 Jan 2017 11:33:39 AM GST
KHADCNPH03-1994530 applprod 2048 Wed 18 Jan 2017 11:41:02 AM GST
SPLDIPPH01-1994538 applprod 2048 Wed 18 Jan 2017 11:42:32 AM GST
SPLDCNPH10-1994642 applprod 2048 Wed 18 Jan 2017 11:46:41 AM GST
[[email protected] ~]# cancel -a
[[email protected] ~]# cancel 1994129
cancel: cancel-job failed: Job #1994129 does not exist!
[[email protected] ~]# lpstat -o
HPDDCNPH06-1994947 applprod 2048 Wed 18 Jan 2017 12:00:42 PM GST
[[email protected] ~]# cancel 1994947
…………………………………………………………..
lpstat -o #to view outstanding print jobs.
cancel -a {printer} # To cancel ALL jobs or …
cancel {printerjobid} # To cancel 1 job.

CUPS Printer configuration on Linux

#ssh Y.Y.Y.Y
#yum install cups
#yum list cups
#mv printers.conf printers.conf_orig #command to take printers.conf backup
#scp X.X.X.X:/etc/cups/printers.conf .
#/etc/init.d/cups restart
#yum install firefox
#scp X.X.X.X:/etc/cups/ppd/* ppd/ #This command to copy existing cups configuration or we can add new printers manually.

How to disable IPV6 on Linux

Method 1:
# echo ‘1’ > /proc/sys/net/ipv6/conf/lo/disable_ipv6
# echo ‘1’ > /proc/sys/net/ipv6/conf/lo/disable_ipv6
# echo ‘1’ > /proc/sys/net/ipv6/conf/all/disable_ipv6
# echo ‘1’ > /proc/sys/net/ipv6/conf/default/disable_ipv6
# /etc/init.d/networking restart

Method 2:
#vi /etc/sysctl.conf
# IPv6 disabled #add these 3 lines in the last
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
# /etc/init.d/networking restart

Method 3 : Disable ipv6 from GRUB

Ipv6 can also be disabled by editing the grub configuration file

$ sudo gedit /etc/default/grub
GRUB_CMDLINE_LINUX=”ipv6.disable=1″
# /etc/init.d/networking restart

Android Malware ‘Judy’ Hits as Many as 36.5 Million Phones

The security firm Checkpoint on Thursday uncovered dozens of Android applications that infected user’s devices with malicious ad-click software. In at least one case, an app bearing the malware was available through the Google Play app store for more than a year.
While the actual extent of the malicious code’s spread is unknown, Checkpoint says it may have reached as many as 36.5 million users, making it potentially the most widely-spread malware yet found on Google Play. Google removed the apps after being notified by Checkpoint.
Get Data Sheet, Fortune’s technology newsletter.
The malicious apps primarily included a series of casual cooking and fashion games under the “Judy” brand, a name borrowed for the malware itself. The nefarious nature of the programs went unnoticed in large part, according to Checkpoint, because its malware payload was downloaded from a non-Google server after the programs were installed. The code would then use the infected phone to click on Google ads, generating fraudulent revenue for the attacker.
The infection may have spread even more widely than Checkpoint’s estimates, since not all of the extensive line of “Judy” apps are included on Checkpoint’s tally – it’s missing Fashion Judy: Magic Girl Style and Fashion Judy: Masquerade Style, among others. All installments of the series do appear to have been pulled from Google Play.
The “Judy” apps were published by an apparently Korean entity known as ENISTUDIO. However, iterations of the same attack were found on a handful of apps from other publishers.This is not the first instance of a malware infestation making it through the screening process on Google Play, nor is it the most damaging – Checkpoint did not find any evidence, for instance, that “Judy” compromised data on infected phones. That Judy was able to hide on Google Play for so long highlights the tradeoffs of Android operating system, which is often seen as more open but less secure than Apple’s iOS.

Start the MySQL server fails

Start the MySQL server fails, as follows:

[[email protected] ~]# /etc/init.d/mysqld start
Starting mysqld (via systemctl): Job for mysqld.service failed because the control process exited with error code. See “systemctl status mysqld.service” and “journalctl -xe” for details.
[FAILED]
When prompted, respectively, using systemctl status mysqld.service and journalctl -xe see why the service failed to start

[[email protected] ~]# systemctl status mysqld.service
?.mysqld.service – SYSV: MySQL database server.
Loaded: loaded (/etc/rc.d/init.d/mysqld)
Active: failed (Result: exit-code) since Wed 2016-01-20 18:26:57 CST; 40s ago
Docs: man:systemd-sysv-generator(8)
Process: 2979 ExecStart=/etc/rc.d/init.d/mysqld start (code=exited, status=1/FAILURE)

Jan 20 18:26:56 spark01 systemd[1]: Starting SYSV: MySQL database server….
Jan 20 18:26:57 spark01 mysqld[2979]: MySQL Daemon failed to start.
Jan 20 18:26:57 spark01 mysqld[2979]: Starting mysqld: [FAILED]
Jan 20 18:26:57 spark01 systemd[1]: mysqld.service: control process exited, code=exited status=1
Jan 20 18:26:57 spark01 systemd[1]: Failed to start SYSV: MySQL database server..
Jan 20 18:26:57 spark01 systemd[1]: Unit mysqld.service entered failed state.
Jan 20 18:26:57 spark01 systemd[1]: mysqld.service failed.

[Root @ spark01 ~] # journalctl truck

— Unit session-2.scope has begun starting up.
Jan 20 18:26:48 spark01 sshd[2916]: pam_unix(sshd:session): session opened for user spark by (uid=0)
Jan 20 18:26:52 spark01 su[2944]: (to root) spark on pts/1
Jan 20 18:26:52 spark01 su[2944]: pam_unix(su-l:session): session opened for user root by spark(uid=1000)
Jan 20 18:26:56 spark01 polkitd[909]: Registered Authentication Agent for unix-process:2974:117137 (system bus name :1.25
Jan 20 18:26:56 spark01 systemd[1]: Starting SYSV: MySQL database server….
— Subject: Unit mysqld.service has begun start-up
— Defined-By: systemd
— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

— Unit mysqld.service has begun starting up.
Jan 20 18:26:57 spark01 mysqld[2979]: MySQL Daemon failed to start.
Jan 20 18:26:57 spark01 mysqld[2979]: Starting mysqld: [FAILED]
Jan 20 18:26:57 spark01 systemd[1]: mysqld.service: control process exited, code=exited status=1
Jan 20 18:26:57 spark01 systemd[1]: Failed to start SYSV: MySQL database server..
— Subject: Unit mysqld.service has failed
— Defined-By: systemd
— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

— Unit mysqld.service has failed.

— The result is failed.
Jan 20 18:26:57 spark01 systemd[1]: Unit mysqld.service entered failed state.
Jan 20 18:26:57 spark01 systemd[1]: mysqld.service failed.
Jan 20 18:26:57 spark01 polkitd[909]: Unregistered Authentication Agent for unix-process:2974:117137 (system bus name :1.

However, when unfortunately, this information does not provide the real reason for the service failed to start.

At this time, it may open the MySQL alarm log, after all, as long as the MySQL service starts, there will be alarm log output information, and sure enough

2016-01-20T10:00:19.935771Z 0 [ERROR] /usr/sbin/mysqld: Can’t create/write to file ‘/var/run/mysqld/mysqld.pid’ (Errcode: 2 – No such file or directory)
2016-01-20T10:00:19.935795Z 0 [ERROR] Can’t start server: can’t create PID file: No such file or directory
160120 18:00:20 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

MySQL service at boot time, you can not create pid file.

In the end look at the directory exists, it really does not exist.

Then, create a / var / run / mysqld / directory, and restart the MySQL service

[[email protected] ~]# mkdir -p /var/run/mysqld/

[[email protected] ~]# /etc/init.d/mysqld start
Starting mysqld (via systemctl): Job for mysqld.service failed because the control process exited with error code. See “systemctl status mysqld.service” and “journalctl -xe” for details.

Still being given to re-view the alarm log, the following output

2016-01-20T10:28:37.183387Z 0 [ERROR] /usr/sbin/mysqld: Can’t create/write to file ‘/var/run/mysqld/mysqld.pid’ (Errcode: 13 – Permission denied)
2016-01-20T10:28:37.183431Z 0 [ERROR] Can’t start server: can’t create PID file: Permission denied
160120 18:28:37 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160120 18:32:06 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql

The original, / var / run / mysqld / or of the owner and group root, mysql and which can not create a file, the owner and the modified directory is a group, started OK.

[[email protected] ~]# ls -ld /var/run/mysqld/
drwxr-xr-x 2 root root 40 Jan 20 18:28 /var/run/mysqld/
[[email protected] ~]# chown mysql.mysql /var/run/mysqld/
[[email protected] ~]# /etc/init.d/mysqld start
Starting mysqld (via systemctl): [ OK ]