[RDD] mysql root PW RRAbuntu

VE4PER / Andy ve4per at aim.com
Sat Jun 11 23:48:07 EDT 2011


Hi Geoff,

I did a complete new clean install, and the installer asks for the mysql 
root
password right during the initial install phase; the RRAbuntu ISO didn't 
do that.

I was under the impression from Frederick's comments that the original 
installer was
used and we would have option to custom partition the hard drive on 
install, rather than
wipe the HD clean, as it does with the Centos/RD2 ISO package.

  Presumably the the full Ubuntu installer would have installed the 
Mysql from scratch and allow everyone full control
of the user table in the mysql db.

It would appear that portion of the original install procedure wasn't 
included in the install script. My curiosity
wonders how then did mysql get included as part of an image?

cheers
Andy


Geoff Barkman wrote:
> Interesting dell370 is the name of my machine that I created the
> rrabuntu iso image on... but not the name of my test machine.
>
> many thanks
> geoff barkman
>
> On Sun, Jun 12, 2011 at 4:49 AM, VE4PER/ Andy<ve4per at aim.com>  wrote:
>    
>> Thanks for your time Benjamin, here is cnf file, also included a couple of
>> comments and the include cnf file as well as excerpt from error.log for
>> mysql
>>
>> ###############################
>> Comments on contents:
>>
>> 1. 'root at dell370' user is apparently a user that exists in the mysql user
>> table that I did not create
>> 2. InnoDB error 11's removed due to sheer numbers of repeated error
>> locking/unlocking ./ibdata1 file in use
>> or non-47existant.
>> 3. I had just followed Frederick's prompts through the install, then near
>> the end it asked for linux user ID and PW
>> and I cancelled at that point to recreate an rduser with install rights and
>> redo it. Then attempted to rdadmin and it
>> asked for mysql root user PW, and received error 11 when it tried to connect
>> and create the RD DB. I then tried CLI access
>> to mysql from a terminal and got the same error. I then used the safe method
>> to reset the password for root only and retried from a terminal window to
>> access mysql; again process was running but got error connecting. I used
>> synaptic package manager, and uninstalled all mysql apps, then restarted box
>> and re-installed mysql apps and retried getting same error.
>>
>> I was about to just reformat and reinstall a clean 10.10 and go from there
>> when I got ur questions. Then the discovery of the extra root user kind of
>> got my curiosity going.
>>
>>
>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>> /etc/mysql/conf.d/mysqld_safe_syslog.cnf
>>
>>
>> [mysqld_safe]
>> syslog
>>
>>
>>
>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>> /etc/mysql/mysql.cnf
>>
>> #
>> # The MySQL database server configuration file.
>> #
>> # You can copy this to one of:
>> # - "/etc/mysql/my.cnf" to set global options,
>> # - "~/.my.cnf" to set user-specific options.
>> #
>> # One can use all long options that the program supports.
>> # Run program with --help to get a list of available options and with
>> # --print-defaults to see which it would actually understand and use.
>> #
>> # For explanations see
>> # http://dev.mysql.com/doc/mysql/en/server-system-variables.html
>>
>> # This will be passed to all mysql clients
>> # It has been reported that passwords should be enclosed with ticks/quotes
>> # escpecially if they contain "#" chars...
>> # Remember to edit /etc/mysql/debian.cnf when changing the socket location.
>> [client]
>> port        = 3306
>> socket        = /var/run/mysqld/mysqld.sock
>>
>> # Here is entries for some specific programs
>> # The following values assume you have at least 32M ram
>>
>> # This was formally known as [safe_mysqld]. Both versions are currently
>> parsed.
>> [mysqld_safe]
>> socket        = /var/run/mysqld/mysqld.sock
>> nice        = 0
>>
>> [mysqld]
>> #
>> # * Basic Settings
>> #
>>
>> #
>> # * IMPORTANT
>> #   If you make changes to these settings and your system uses apparmor, you
>> may
>> #   also need to also adjust /etc/apparmor.d/usr.sbin.mysqld.
>> #
>>
>> user        = mysql
>> socket        = /var/run/mysqld/mysqld.sock
>> port        = 3306
>> basedir        = /usr
>> datadir        = /var/lib/mysql
>> tmpdir        = /tmp
>> skip-external-locking
>> #
>> # Instead of skip-networking the default is now to listen only on
>> # localhost which is more compatible and is not less secure.
>> bind-address        = 127.0.0.1
>> #
>> # * Fine Tuning
>> #
>> key_buffer        = 16M
>> max_allowed_packet    = 16M
>> thread_stack        = 192K
>> thread_cache_size       = 8
>> # This replaces the startup script and checks MyISAM tables if needed
>> # the first time they are touched
>> myisam-recover         = BACKUP
>> #max_connections        = 100
>> #table_cache            = 64
>> #thread_concurrency     = 10
>> #
>> # * Query Cache Configuration
>> #
>> query_cache_limit    = 1M
>> query_cache_size        = 16M
>> #
>> # * Logging and Replication
>> #
>> # Both location gets rotated by the cronjob.
>> # Be aware that this log type is a performance killer.
>> # As of 5.1 you can enable the log at runtime!
>> #general_log_file        = /var/log/mysql/mysql.log
>> #general_log             = 1
>>
>> log_error                = /var/log/mysql/error.log
>>
>> # Here you can see queries with especially long duration
>> #log_slow_queries    = /var/log/mysql/mysql-slow.log
>> #long_query_time = 2
>> #log-queries-not-using-indexes
>> #
>> # The following can be used as easy to replay backup logs or for
>> replication.
>> # note: if you are setting up a replication slave, see README.Debian about
>> #       other settings you may need to change.
>> #server-id        = 1
>> #log_bin            = /var/log/mysql/mysql-bin.log
>> expire_logs_days    = 10
>> max_binlog_size         = 100M
>> #binlog_do_db        = include_database_name
>> #binlog_ignore_db    = include_database_name
>> #
>> # * InnoDB
>> #
>> # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
>> # Read the manual for more InnoDB related options. There are many!
>> #
>> # * Security Features
>> #
>> # Read the manual, too, if you want chroot!
>> # chroot = /var/lib/mysql/
>> #
>> # For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
>> #
>> # ssl-ca=/etc/mysql/cacert.pem
>> # ssl-cert=/etc/mysql/server-cert.pem
>> # ssl-key=/etc/mysql/server-key.pem
>>
>>
>>
>> [mysqldump]
>> quick
>> quote-names
>> max_allowed_packet    = 16M
>>
>> [mysql]
>> #no-auto-rehash    # faster start of mysql but no tab completition
>>
>> [isamchk]
>> key_buffer        = 16M
>>
>> #
>> # * IMPORTANT: Additional settings that can override those from this file!
>> #   The files must end with '.cnf', otherwise they'll be ignored.
>> #
>> !includedir /etc/mysql/conf.d/
>>
>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>> /var/log/mysql/error.log
>> 100521  8:19:55 [Note] Plugin 'FEDERATED' is disabled.
>> InnoDB: The first specified data file ./ibdata1 did not exist:
>> InnoDB: a new database to be created!
>> 100521  8:19:55  InnoDB: Setting file ./ibdata1 size to 10 MB
>> InnoDB: Database physically writes the file full: wait...
>> 100521  8:19:56  InnoDB: Log file ./ib_logfile0 did not exist: new to be
>> created
>> InnoDB: Setting log file ./ib_logfile0 size to 5 MB
>> InnoDB: Database physically writes the file full: wait...
>> 100521  8:19:56  InnoDB: Log file ./ib_logfile1 did not exist: new to be
>> created
>> InnoDB: Setting log file ./ib_logfile1 size to 5 MB
>> InnoDB: Database physically writes the file full: wait...
>> InnoDB: Doublewrite buffer not found: creating new
>> InnoDB: Doublewrite buffer created
>> InnoDB: Creating foreign key constraint system tables
>> InnoDB: Foreign key constraint system tables created
>> 100521  8:19:56  InnoDB: Started; log sequence number 0 0
>> 100521  8:19:56  InnoDB: Starting shutdown...
>> 100521  8:19:58  InnoDB: Shutdown completed; log sequence number 0 44233
>> 100521  8:19:58 [Note] Plugin 'FEDERATED' is disabled.
>> 100521  8:19:58  InnoDB: Started; log sequence number 0 44233
>> 100521  8:19:58  InnoDB: Starting shutdown...
>> 100521  8:19:59  InnoDB: Shutdown completed; log sequence number 0 44233
>> 100521  8:19:59 [Note] Plugin 'FEDERATED' is disabled.
>> 110608 16:23:54  InnoDB: Started; log sequence number 0 44233
>> 110608 16:23:54 [Warning] Found invalid password for user: 'root at localhost';
>> Ignoring user
>> 110608 16:23:54 [Warning] Found invalid password for user: 'root at dell370';
>> Ignoring user
>> 110608 16:23:54 [Warning] Found invalid password for user: 'root at 127.0.0.1';
>> Ignoring user
>> 110608 16:23:54 [Note] Event Scheduler: Loaded 0 events
>> 110608 16:23:54 [Note] /usr/sbin/mysqld: ready for connections.
>> Version: '5.1.41-3ubuntu12.10'  socket: '/var/run/mysqld/mysqld.sock'  port:
>> 3306  (Ubuntu)
>> 110608 16:27:39 [Note] /usr/sbin/mysqld: Normal shutdown
>> 110608 16:27:39 [Note] Event Scheduler: Purging the queue. 0 events
>> 110608 16:27:39  InnoDB: Starting shutdown...
>> 110608 16:27:39  InnoDB: Shutdown completed; log sequence number 0 44233
>> 110608 16:27:39 [Note] /usr/sbin/mysqld: Shutdown complete
>> 110608 16:27:49 [Note] Plugin 'FEDERATED' is disabled.
>> 110608 16:27:50  InnoDB: Started; log sequence number 0 44233
>> 110608 16:27:50 [Warning] Found invalid password for user: 'root at localhost';
>> Ignoring user
>> 110608 16:27:50 [Warning] Found invalid password for user: 'root at dell370';
>> Ignoring user
>> 110608 16:27:50 [Warning] Found invalid password for user: 'root at 127.0.0.1';
>> Ignoring user
>> 110608 16:27:50 [Note] Event Scheduler: Loaded 0 events
>> 110608 16:27:50 [Note] /usr/sbin/mysqld: ready for connections.
>> Version: '5.1.41-3ubuntu12.10'  socket: '/var/run/mysqld/mysqld.sock'  port:
>> 3306  (Ubuntu)
>> 110608 16:28:11 [Note] /usr/sbin/mysqld: Normal shutdown
>> 110608 16:28:11 [Note] Event Scheduler: Purging the queue. 0 events
>> 110608 16:28:11  InnoDB: Starting shutdown...
>> 110608 16:28:12  InnoDB: Shutdown completed; log sequence number 0 44233
>> 110608 16:28:12 [Note] /usr/sbin/mysqld: Shutdown complete
>> 110608 16:29:01 [Note] Plugin 'FEDERATED' is disabled.
>> 110608 16:29:01  InnoDB: Started; log sequence number 0 44233
>> 110608 16:29:01 [Warning] Found invalid password for user: 'root at localhost';
>> Ignoring user
>> 110608 16:29:01 [Warning] Found invalid password for user: 'root at dell370';
>> Ignoring user
>> 110608 16:29:01 [Warning] Found invalid password for user: 'root at 127.0.0.1';
>> Ignoring user
>> 110608 16:29:01 [Note] Event Scheduler: Loaded 0 events
>> 110608 16:29:01 [Note] /usr/sbin/mysqld: ready for connections.
>> Version: '5.1.41-3ubuntu12.10'  socket: '/var/run/mysqld/mysqld.sock'  port:
>> 3306  (Ubuntu)
>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>>
>>
>>
>> ######################################################################
>>
>> -----Original Message-----
>> From: Benjamin D. Fillmore<benjamin at fillmoretechnical.com>
>> To: User discussion about the Rivendell Radio Automation System
>> <rivendell-dev at lists.rivendellaudio.org>
>> Sent: Sat, Jun 11, 2011 4:24 pm
>> Subject: Re: [RDD] mysql root PW RRAbuntu
>>
>> Can you paste your my.cnf file contents?
>>
>>
>>
>>
>>
>> Thanks
>>
>>
>>
>>
>>
>> On 6/11/2011 8:34 AM, VE4PER / Andy wrote:
>>
>>
>>      
>>> Benjamin D Fillmore wrote:
>>>        
>>
>>      
>>>> To make sure I'm understanding you...
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>> You did the procedure, reset the password, and restarted the mysql
>>>> daemon.
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>> On the local system, can you then connect via CLI?:   mysql -u root -p
>>>>          
>>
>>      
>>>>          
>>
>>      
>>> NO Generates same no connection to socket error.
>>>        
>>
>>      
>>>        
>>
>>      
>>>> If not, can you verify that the mysql service still actually running?
>>>>          
>>
>>      
>>>> ps aux | grep mysql
>>>>          
>>
>>      
>>>>          
>>
>>      
>>> Yes it is
>>>        
>>
>>      
>>>        
>>
>>      
>>>> If not, you may want toenable general logging in the my.cnf file.
>>>>          
>>
>>      
>>>>          [mysqld]
>>>>          
>>
>>      
>>>>           log = /var/log/mysqld.log
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>> Do not leave this enabled for anything other than troubleshooting,
>>>>          
>>
>>      
>>>> debugging an issue.
>>>>          
>>
>>      
>>>> It is a serious performance hit.
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>> There should also be a mysql error log for you to check.
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>> I can't think of any other reason (other than it not running) for a
>>>>          
>>
>>      
>>>> default install of mysql to not accept connections from localhost, to
>>>>          
>>
>>      
>>>> localhost.
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>> I've been through the procedure I pasted a hundred times to reset admin
>>>>          
>>
>>      
>>>> passwords -- never had a problem so far.
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>> Let me know the answers to the first couple questions, and I'll see if I
>>>>          
>>
>>      
>>>> can come up with any additional advice for you....   :)
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>>          
>>
>>      
>>> I am hoping to find a solution as I am on a data capped connection here,
>>> and
>>>        
>>
>>      
>>> although re-installing is OK, I don't need the extra data charges the OS
>>>        
>>
>>      
>>> updates etc. incur.
>>>        
>>
>>      
>>>        
>>
>>      
>>> Frederick's scripts appeared to autostart, then I did a cancel at the
>>>        
>>
>>      
>>> end to restart them, and when I
>>>        
>>
>>      
>>> finished checking to see that apache and mysqld were running was when I
>>>        
>>
>>      
>>> noticed they had to be installed
>>>        
>>
>>      
>>> and started as well. When I tried rdadmin and it asked for mysql root
>>>        
>>
>>      
>>> and pw was when the connect error
>>>        
>>
>>      
>>> occurred first; and all other attempts to connect have same error. Might
>>>        
>>
>>      
>>> have to re-install after all; just hate to
>>>        
>>
>>      
>>> after all the efforts to get it to the point it is at now.
>>>        
>>
>>      
>>>        
>>
>>      
>>> I don't mind if there is no alternative...
>>>        
>>
>>      
>>>> On 6/10/2011 11:48 AM, VE4PER / Andy wrote:
>>>>          
>>
>>      
>>>>          
>>
>>      
>>>>> Yes I did skip grant tables on running safe.... stopped mysqld, started
>>>>>            
>>
>>      
>>>>> mysqld_safe skipping grant
>>>>>            
>>
>>      
>>>>>            
>>
>>      
>>>>> did everything you quoted here as outlined, then restarted mysqld
>>>>>            
>>
>>      
>>>>>            
>>
>>      
>>>>> tried MySQLAdmin gui and wouldn't connect to localhost, 127.0.0.1 at all
>>>>>            
>>
>>      
>>>>> using default port and root user
>>>>>            
>>
>>      
>>>>> and new password.
>>>>>            
>>
>>      
>>>>>            
>>
>>      
>>>>> When I ran the safe mode, it all appeared to work fine as if the new
>>>>>            
>>
>>      
>>>>> password was implemented.
>>>>>            
>>
>>      
>>>>>            
>>
>>      
>>>>>            
>>
>>      
>>>>>            
>>
>>      
>>>>> Benjamin D Fillmore wrote:
>>>>>            
>>
>>      
>>>>>            
>>
>>      
>>>>>> Are you also skipping grant tables?
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>         Subject
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>> Recover a mySQL root Password
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>         Contents
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>             Stop the MySQL server process.
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>> # /etc/init.d/mysql stop
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>             Start again with no grant tables.
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>          # mysqld_safe --skip-grant-tables&
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>             Login to MySQL as root.
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>          # mysql -u root
>>>>>>              
>>
>>      
>>>>>>          mysql>     use mysql;
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>             Set new password.
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>          mysql>     update user set password=PASSWORD("newrootpassword")
>>>>>>              
>>
>> where
>>
>>
>>      
>>>>>> User='root';
>>>>>>              
>>
>>      
>>>>>>          mysql>     flush privileges;
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>             Exit MySQL
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>          mysql>     quit
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>             ...and restart MySQL server.
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>          # /etc/init.d/mysql stop
>>>>>>              
>>
>>      
>>>>>>          # /etc/init.d/mysql start
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>> On 6/10/2011 9:49 AM, VE4PER / Andy wrote:
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>> Anybody have PW for mysql in the initial RRAbuntu install ?
>>>>>>>                
>>
>>      
>>>>>>>                
>>
>>      
>>>>>>> I am unable to log in to mysql as mysql root; tried resetting PW using
>>>>>>>                
>>
>>      
>>>>>>> mysqld_safe
>>>>>>>                
>>
>>      
>>>>>>> option still no go. Unable to access via mysql command with
>>>>>>> mysqld_safe
>>>>>>>                
>>
>>      
>>>>>>> running either.
>>>>>>>                
>>
>>      
>>>>>>>                
>>
>>      
>>>>>>> I keep getting non-existent socket error.
>>>>>>>                
>>
>>      
>>>>>>>                
>>
>>      
>>>>>>> Thanks
>>>>>>>                
>>
>>      
>>>>>>> Andy
>>>>>>>                
>>
>>      
>>>>>>> _______________________________________________
>>>>>>>                
>>
>>      
>>>>>>> Rivendell-dev mailing list
>>>>>>>                
>>
>>      
>>>>>>> Rivendell-dev at lists.rivendellaudio.org
>>>>>>>                
>>
>>      
>>>>>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>>>>>>>                
>>
>>      
>>>>>>>                
>>
>>      
>>>>>>>                
>>
>>      
>>>>>> _______________________________________________
>>>>>>              
>>
>>      
>>>>>> Rivendell-dev mailing list
>>>>>>              
>>
>>      
>>>>>> Rivendell-dev at lists.rivendellaudio.org
>>>>>>              
>>
>>      
>>>>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>>>              
>>
>>      
>>>>> _______________________________________________
>>>>>            
>>
>>      
>>>>> Rivendell-dev mailing list
>>>>>            
>>
>>      
>>>>> Rivendell-dev at lists.rivendellaudio.org
>>>>>            
>>
>>      
>>>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>>>>>            
>>
>>      
>>>>>            
>>
>>      
>>>> _______________________________________________
>>>>          
>>
>>      
>>>> Rivendell-dev mailing list
>>>>          
>>
>>      
>>>> Rivendell-dev at lists.rivendellaudio.org
>>>>          
>>
>>      
>>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>>>>          
>>
>>      
>>>>          
>>
>>      
>>> _______________________________________________
>>>        
>>
>>      
>>> Rivendell-dev mailing list
>>>        
>>
>>      
>>> Rivendell-dev at lists.rivendellaudio.org
>>>        
>>
>>      
>>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>>>        
>>
>> _______________________________________________
>>
>>
>> Rivendell-dev mailing list
>>
>>
>> Rivendell-dev at lists.rivendellaudio.org
>>
>>
>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>>
>>
>>
>> _______________________________________________
>> Rivendell-dev mailing list
>> Rivendell-dev at lists.rivendellaudio.org
>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>>
>>
>>      
> _______________________________________________
> Rivendell-dev mailing list
> Rivendell-dev at lists.rivendellaudio.org
> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
>    



More information about the Rivendell-dev mailing list