No MySQL users after fresh install in RHEL 6.6

I had a fresh install of RHEL 6.6 with MySQL 5.1.73. When i tried to reset MySQL root password for MySQL, it hadn’t worked. Reason was, that mysql.user table was empty, there was no ‘root’ user created.

Following helped me to resolve the issue:

  1. Restart MySQL like this:
    service mysqld restart --skip-grant-tables
  2. Enter MySQLfrom the command line (no password needed at this point)
    # mysql
  3. Do desc mysql.user

    You will see 17 rows for MySQL 4.1
    You will see 37 rows for MySQL 5.0
    You will see 39 rows for MySQL 5.1
    You will see 42 rows for MySQL 5.5

    You will have to tweak each privilege since the GRANT command does not work will skip-grant-tables is enabled

  4. For MySQL 5.1, you can enter a new root@localhost whose password is ‘whatever’ as follows:

    DELETE FROM mysql.user WHERE user='root' AND host='localhost';
    INSERT INTO mysql.user SET
                      Host = 'localhost',
                      User = 'root',
                  Password = PASSWORD('whatever'),
               Select_priv = 'Y',
               Insert_priv = 'Y',
               Update_priv = 'Y',
               Delete_priv = 'Y',
               Create_priv = 'Y',
                 Drop_priv = 'Y',
               Reload_priv = 'Y',
             Shutdown_priv = 'Y',
              Process_priv = 'Y',
                 File_priv = 'Y',
                Grant_priv = 'Y',
           References_priv = 'Y',
                Index_priv = 'Y',
                Alter_priv = 'Y',
              Show_db_priv = 'Y',
                Super_priv = 'Y',
     Create_tmp_table_priv = 'Y',
          Lock_tables_priv = 'Y',
              Execute_priv = 'Y',
           Repl_slave_priv = 'Y',
          Repl_client_priv = 'Y',
          Create_view_priv = 'Y',
            Show_view_priv = 'Y',
       Create_routine_priv = 'Y',
        Alter_routine_priv = 'Y',
          Create_user_priv = 'Y',
                Event_priv = 'Y',
              Trigger_priv = 'Y',
                  ssl_type = '',
                  ssl_cipher = '',
                 x509_issuer = '',
                x509_subject = '',
               max_questions = 0,
                 max_updates = 0;

  5. Restart MySQL
    service mysqld restart

Source: Database Administrators Stack Exchange

Cannot sign-in to Nokia Account via Nokia Suite

I could connect to my account from the phone (Nokia C7) and I could also reach my account on internet, but I was not able to sign-in to my account in Nokia Suite.

Nokia Suite connects to the server and For these servers, SSL 3 was disabled on October 15th 2014. As of today, these servers require TLS 1.0. Nokia Suite does not use TLS 1.0 but only SSL 3, because Nokia Suite uses the QT framework 4.7.4. Up to that version, the QtNetwork class QSslSocket used SSL 3 and not TLS 1.0 as default protocol.

Issue can be resolved by replacing a DLL file:

  1. exit the Nokia Suite via right-click in (bottom, left) Windows Notification Area (system tray)
  2. download this modified version of ssleay32.dll (local copy for a case it would get deleted
  3. replace this file at C:\Program Files (x86)\Nokia\Nokia Suite\

Source: Nokia Support Discussions

Digital IBMer 2014 – Internet Explorer 11 facing like IE7 issue

From server perspective everything with Digital IBMer 2014 works fine. But end-users reported strange behavior: some pages were empty for them.

Digital IBMer 2014 IE11 issue     Digital IBMer 2014 in FF is ok

Steps taken

  1. Tried to reproduce the issue on test environment … issue was not reproducible, it appears in production only
  2. Checked IHS (Apache) access and error logs … they were clear, no issue
  3. Checked connection statistics (netstats) to see if we are not hitting limits … stats were OK
  4. Tried to reproduce issue in Firefox with Firebug … issue not reproducible, all requests made to server were returned with HTTP 200 (OK)
  5. Tried to reproduce issue in IE11 with Fiddler … issue reproducible, but Fiddler shown no issue, all requests were returned again with HTTP 200 (OK)
  6. Checked if files in cache are equal to files on server … files were OK
  7. Check of page in IE using F12 Developer Tools … Network tool confirmed all files were received OK, Console shown no issues, in DOM Inspector everything seemed all right


As issue was reproducible only in IE11 and not in other browsers (IE9, Firefox, Chrome, Safari), we were sure issue is not on our servers, but on the course side. We engaged developer of the course, guy from India, DOJO and browser expert. It took him about 10 minutes to identify the issue.

IE11 Compatibility Mode settings

Problem was that somehow IBM internal servers made it to the Microsoft compatibility list, and so the production server pages were rendered in IE7 compatibility mode. And this caused Framework malfunction. Helpdesk was instructed to suggest to users to turn of both checkboxes in Compatibility View settings and make sure is not listed within Compatibility Mode Websites, what resolved the issue.

Digital IBMer 2014 – Context and History

As you (maybe) know, I work in IBM on development and support of Learning Management System. Every year we are faced with challenge of so called Digital IBMer course. It’s course which educates IBMers on the latest cybersecurity threats, and all IBM employees need to go through it every year. From our perspective that means few thousands unique users in addition to standard daily load, and usually all those users try to make the course in about same timeframe (1-2 peak hours).

Digital IBMer 2012 was mainly about tuning our WebSphere App Server and DB2 configuration. During Digital IBMer 2013 shared proxies were the main blocker (there is a limit of incoming connections for each application).

For this year we worked pretty hard since last October to make whole environment ready. We’ve got our own dedicated proxy server, we’ve ran extensive performance testing, there was setup a super-cool monitoring tool ITCAM to help us analyze the system, we’ve added some other monitors on OS level based on various performance analysis experts advices, and in cooperation with AIX, DB2 and WAS L2 support we’ve tuned our environment settings. Simply said – we’ve made everything ready.

This should have been first year without any issues… 🙂