Jul 15 10:10:52 vlevcenter01 checkproc: checkproc: Empty pid file. It looks like it can't create the pid files for the services because there is no.
I'm having trouble connecting to the mysql database, MySQL Administrator is giving an error about not being able to find the socket. 'Could not connect to host 'localhost'.
MySQL Error Nr. 2002 Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'(2)' When I use the Ping Host button it does find the host. On Sun, 2009-05-17 at 23:29 +0200, Anders Johansson wrote: On Sunday 17 May 2009 23:22:08 Mike McMullin wrote: -rw-r-r- 1 root root 0 2009-05-16 16:41 mysqld.pid The pid file is 0 bytes large. Are you sure mysql is running at all? Yast-System-System Services indicates Yes. (with the astersisk), CLI result as root: rcmysql status Checking for service MySQL: checkproc: Empty pid file /var/lib/mysql/mysqld.pid for /usr/sbin/mysqld unused - To unsubscribe, e-mail: For additional commands, e-mail. On Sun, 2009-05-17 at 23:29 +0200, Anders Johansson wrote: On Sunday 17 May 2009 23:22:08 Mike McMullin wrote: -rw-r-r- 1 root root 0 2009-05-16 16:41 mysqld.pid The pid file is 0 bytes large.
Are you sure mysql is running at all? Yast-System-System Services indicates Yes. (with the astersisk)CLI result as root: rcmysql status Checking for service MySQL: checkproc: Empty pid file /var/lib/mysql/mysqld.pid for /usr/sbin/mysqld unused Exactly, but the best way would be ps aux grep mysql If it isn't, try starting it by hand rcmysql start and see if you get any error messages. You probably also want to check log files Anders - To unsubscribe, e-mail: For additional commands, e-mail. On Sunday 17 May 2009 23:34:08 Mike McMullin wrote: On Sun, 2009-05-17 at 23:29 +0200, Anders Johansson wrote: On Sunday 17 May 2009 23:22:08 Mike McMullin wrote: -rw-r-r- 1 root root 0 2009-05-16 16:41 mysqld.pid The pid file is 0 bytes large.
Are you sure mysql is running at all? Yast-System-System Services indicates Yes. (with the astersisk)CLI result as root: rcmysql status Checking for service MySQL: checkproc: Empty pid file /var/lib/mysql/mysqld.pid for /usr/sbin/mysqld unused Exactly, but the best way would be ps aux grep mysql ps aux grep mysql root 14781 0.0 0.0 3232 748 pts/5 S+ 17:56 0:00 grep mysql If it isn't, try starting it by hand rcmysql start and see if you get any error messages. You probably also want to check log files rcmysql start checkproc: Empty pid file /var/lib/mysql/mysqld.pid for /usr/sbin/mysqld Updating MySQL privilege database. Failed From /var/log/mysqld.log: 090517 17:57:40 mysqld started 090517 17:57:41 ERROR /usr/sbin/mysqld: unknown variable 'binlogformat=mixed' 090517 17:57:41 mysqld ended - To unsubscribe, e-mail: For additional commands, e-mail. On Monday 18 May 2009 00:02:18 Mike McMullin wrote: 090517 17:57:40 mysqld started 090517 17:57:41 ERROR /usr/sbin/mysqld: unknown variable 'binlogformat=mixed' 090517 17:57:41 mysqld ended Am I right in thinking that you have been playing with newer versions of mysql on this system? This looks like you're trying to start mysqld with a configuration file for a much newer version of mysql.
The binlogformat variable wasn't added until version 5.1.5 according to the mysql docs Anders - To unsubscribe, e-mail: For additional commands, e-mail. On Mon, 2009-05-18 at 00:20 +0200, Anders Johansson wrote: On Monday 18 May 2009 00:02:18 Mike McMullin wrote: 090517 17:57:40 mysqld started 090517 17:57:41 ERROR /usr/sbin/mysqld: unknown variable 'binlogformat=mixed' 090517 17:57:41 mysqld ended Am I right in thinking that you have been playing with newer versions of mysql on this system? Yes, then I switched back. This looks like you're trying to start mysqld with a configuration file for a much newer version of mysql. The binlogformat variable wasn't added until version 5.1.5 according to the mysql docs So the uninstall and downgrade to the original install version didn't work.
I looked at the various my.cnf. files in /etc and all but the my.cnf.rpmnew had a reference to binlog format=mixed.
After mv the my.cnf for back, i did a cp my.cnf.rpmnew my.cnf and this was the result: rcmysql start checkproc: Empty pid file /var/lib/mysql/mysqld.pid for /usr/sbin/mysqld Updating MySQL privilege database. Looking for 'mysql' in: /usr/bin/mysql Looking for 'mysqlcheck' in: /usr/bin/mysqlcheck Running 'mysqlcheck'.
![Jenkins dead but pid file exists Jenkins dead but pid file exists](http://www.djack.com.pl/fq_img10/img_10.jpg)
The investigation, I believe, has come up truly empty on its central charge related to the president — collusion with the Russian government. They are now trying to find someone, anyone who had any contact with Julian Assange with the aim of calling that collusion-lite. But mostly what Mueller’s team is doing is bludgeoning witnesses on unrelated charges to piece together a case against the president. They are shaping that case through the indictments - and threats of indictments - that are being used to get guilty pleas to make the president seem like an obstructor or co-conspirator. They are literally creating the crimes.
Let’s review what Mueller and his team are doing. Michael Flynn — They discovered unreported lobbying by Trump's former National Security Adviser and leveraged that to get him to plead guilty to lying to the FBI. So that they can claim Trump’s comment to James Comey about letting him go was obstruction of justice. Yet no other prosecutor would ever have brought this charge.
Michael Cohen — They got Trump’s former lawyer on all sorts of financial crimes related to his businesses and loans. But he pled guilty to campaign finance violations for payments that in the past would have been ruled on as personal expenses.
Now they’ve also gotten him to cop to lying about when he killed the perfectly legal Russia tower project, only it appears that Trump’s lawyers ducked that perjury trap in the written questions. George Papadopoulos— The former member of Trump’s foreign policy advisory panel was forced to plead to lying about the timing of his contacts. The goal was to legitimize the start of the investigation around him when all he did was pass on a surmise or a tip he received. Was the time and expense worth a 14-day sentence? Of course not. They had all the records they needed to figure out who he contacted when.
Jerome Corsi – The best-selling author was threatened with pleading to lying about his contacts with his friend and former Trump campaign adviser Roger Stone. There was nothing illegal about his comments or actions, and he is a journalist, though obviously, the general rules of journalism don’t apply to conservatives like him. Roger Stone - The former Trump campaign adviser sent out a tweet suggesting Hillary Clinton’s campaign chairman John Podesta was next, and an email to Corsi asking him to get the rest of the emails.
He was obviously trying to find out what was going on with these emails, and that’s not illegal in any way. Paul Manafort – The former Trump presidential campaign chairman’s old tax and reporting cases going far back were dusted off to get him under the thumb of the prosecutor. It was revealed that he continued a joint defense agreement with the president and suddenly the prosecutor is saying he lied about his business dealings.
![Could Could](https://bethebeast.pl/wp-content/uploads/2016/11/jenkins-job-config2.png)
It’s all about vengeance on him for failing to give them what they want and to make Trump look bad. Sure, there are some anonymous Russians who will never be tried to add on top of this record.
But it’s clear now Mueller is no longer looking for crimes in the presidential race of 2016. He is simply creating a narrative to delegitimize the president and to string together his words to Comey with the Flynn indictment, Cohen with Stormy Daniels payment, Roger Stone and Jerome Corsi with ties to Julian Assange, and now Cohen with underplaying Russia connections. And let’s not forget the Trump Tower meeting with the attorney who was also conveniently working with Fusion GPS. There’s no doubt that the outline of Mueller’s report was written a long time ago and is being filled in. For those who thought Mueller would deliver a balanced and thoughtful report, these latest actions suggest that instead, we are seeing an all-out attack on the president and the presidency the likes of which we have never seen. Get ready for the fight of the century coming soon and it will be about everything except collusion with the Russian government.