[ZendTo] problem installing zend.to with installer script

Wed Mar 8 17:38:13 GMT 2017

The /etc/apparmor.d/usr.sbin.mysqld file should end with this:

#include <local/usr.sbin.mysqld>

which means that you just put your local additions in the 
/etc/apparmor.d/local/... file, and not everything.

I'm wondering if it was actually just the permissions on the 
/etc/apparmor.d/local/usr.sbin.mysqld file that my installer wrote.
If AppArmor couldn't read it for some reason, that would certainly 
explain what you saw.

Cheers,
Jules.

On 08/03/2017 17:17, Greg Marshall wrote:
> FYI,
> I figured out my issue and wanted to report back.
>
> AppArmor was preventing MySQL from having access. The install script 
> adds a line into
> /etc/apparmor.d/local/usr.sbin.mysqld
> but in my case, that file didn't exist to begin with, so only the 
> zend.to specific rule was in there, not all the MySQL defaults.
>
> I copied
> /etc/apparmor.d/usr.sbin.mysqld
> to
> /etc/apparmor.d/local/
> (making it /etc/apparmor.d/local/usr.sbin.mysqld)
> and then it all worked.
>
> Greg
>
> Truman State University
>
> Greg Marshall
> Web Services Manager
> IT Services
> Truman State University
> 111C McClain Hall
> 100 E. Normal Avenue
> Kirksville, MO 63501
> (660) 785-4254
> gmarsh at truman.edu <mailto:gmarsh at truman.edu>
> www.truman.edu <http://www.truman.edu>
> Don’t follow.  Pursue.
>
>
>> On Mar 2, 2017, at 2:45 PM, Greg Marshall <gmarsh at truman.edu 
>> <mailto:gmarsh at truman.edu>> wrote:
>>
>> Hi,
>> I'm trying to do a new install of zend.to on Ubuntu 14.04 (64 bit) 
>> using the installer script.
>>
>> It crashes out trying to set up MySQL with PHP. I know MySQL isn't 
>> needed for the system any more, but apparently it gets installed so 
>> the PHP tests pass, and then gets removed again.
>>
>> The output from this part of the install process is below. (stdout 
>> and stderr are combined, so it's a little weird). Note that I 
>> uninstalled MySQL prior to running the installer this last time, so 
>> there's no other process running. I've also tried setting the 
>> permissions to 777... It doesn't seem to be a permissions issue.
>>
>> Does anybody know what's going on?
>>
>> Thanks,
>> Greg
>>
>>
>> + /usr/sbin/mysqld --no-defaults --user=mysql 
>> --bind-address=127.0.0.1 --port=2766 
>> --socket=/root/zendto-build-store/php5-5.5.9+dfsg/mysql_db/mysql.sock 
>> --datadir=/root/zendto-build-store/php5-5.5.9+dfsg/mysql_db 
>> --bootstrap --skip-grant-tables
>> 170302 12:44:24 [Note] Ignoring --secure-file-priv value as server is 
>> running with --bootstrap.
>> 170302 12:44:24 [Note] /usr/sbin/mysqld (mysqld 
>> 5.5.54-0ubuntu0.14.04.1) starting as process 19855 ...
>> 170302 12:44:24 [Note] Plugin 'FEDERATED' is disabled.
>> 170302 12:44:24 InnoDB: The InnoDB memory heap is disabled
>> 170302 12:44:24 InnoDB: Mutexes and rw_locks use GCC atomic builtins
>> 170302 12:44:24 InnoDB: Compressed tables use zlib 1.2.8
>> 170302 12:44:24 InnoDB: Using Linux native AIO
>> 170302 12:44:24 InnoDB: Initializing buffer pool, size = 128.0M
>> 170302 12:44:24 InnoDB: Completed initialization of buffer pool
>> InnoDB: Unable to lock ./ibdata1, error: 13
>> InnoDB: Check that you do not already have another mysqld process
>> InnoDB: using the same InnoDB data or log files.
>> 170302 12:44:24  InnoDB: Operating system error number 13 in a file 
>> operation.
>> InnoDB: The error means mysqld does not have the access rights to
>> InnoDB: the directory.
>> InnoDB: Error in creating or opening ./ibdata1
>> 170302 12:44:24 InnoDB: Could not open or create data files.
>> 170302 12:44:24 InnoDB: If you tried to add new data files, and it 
>> failed here,
>> 170302 12:44:24 InnoDB: you should now edit innodb_data_file_path in 
>> my.cnf back
>> 170302 12:44:24 InnoDB: to what it was, and remove the new ibdata 
>> files InnoDB created
>> 170302 12:44:24 InnoDB: in this failed attempt. InnoDB only wrote 
>> those files full of
>> 170302 12:44:24 InnoDB: zeros, but did not yet use them in any way. 
>> But be careful: do not
>> 170302 12:44:24 InnoDB: remove old data files which contain your 
>> precious data!
>> 170302 12:44:24 [ERROR] Plugin 'InnoDB' init function returned error.
>> 170302 12:44:24 [ERROR] Plugin 'InnoDB' registration as a STORAGE 
>> ENGINE failed.
>> 170302 12:44:24 [ERROR] Unknown/unsupported storage engine: InnoDB
>> 170302 12:44:24 [ERROR] Aborting
>>
>> 170302 12:44:24 [Note] /usr/sbin/mysqld: Shutdown complete
>>
>> make: *** [test-results.txt] Error 1
>> ^[[1m ^[[0m
>> ^[[1mOh dear, building PHP failed. I am going to need help.^[[0m
>> ^[[1mPlease try to fix whatever was wrong and re-run this script.^[[0m
>> ^[[1mExiting...^[[0m
>>
>>
>>
>>
>> Truman State University
>>
>> Greg Marshall
>> Web Services Manager
>> IT Services
>> Truman State University
>> 111C McClain Hall
>> 100 E. Normal Avenue
>> Kirksville, MO 63501
>> (660) 785-4254
>> gmarsh at truman.edu <mailto:gmarsh at truman.edu>
>> www.truman.edu <http://www.truman.edu>
>> Don’t follow.  Pursue.
>>
>>
>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://mailman.ecs.soton.ac.uk/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng MBCS CITP CEng

'Once is happenstance, twice is coincidence, three times is enemy
  action.' - Ian Fleming

www.Zend.To
Twitter: @JulesFM
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/zendto/attachments/20170308/c2cc9ee0/attachment.html 