Solved CentOS 7 VM will not boot
-
Oh database files, that sucks. What DB engine is it? MyISAM? InnoDB? Something else?
-
@scottalanmiller said:
Oh database files, that sucks. What DB engine is it? MyISAM? InnoDB? Something else?
Wordpress database. running on centos7. so it is mariadb
-
MariaDB is an RDBMS. It isn't a DB engine. It uses other engines. MyISAM and InnoDB are the two most common. There is no MariaDB database engine option.
-
http://daerma.com now loads. the rest popped up the initial wordpress config. going to recopy the db files from the mysql folder
-
@JaredBusch said:
http://daerma.com now loads. the rest popped up the initial wordpress config. going to recopy the db files from the mysql folder
daerma.com is giving me some weird permission error too .i cannot install a plugin or theme, because it pops the FTP login info like my old install did. but I chown'd the wp directory to apache:apache. not sure what is up.
-
well i have been unable to recover everything correctly by copying from the drive that was originally attached.
Would it be possible to copy the boot partitions to the old drive and then try and attach it as the primary drive? That is more in depth CentOS than I know how to handle.
-
At this point I think i will just nuke and rebuild from scratch if I cannot copy the boot partition and have the system come back up. Going to be out all afternoon with the family so looking forward to any ideas you all come up with.
-
@JaredBusch said:
@JaredBusch said:
http://daerma.com now loads. the rest popped up the initial wordpress config. going to recopy the db files from the mysql folder
daerma.com is giving me some weird permission error too .i cannot install a plugin or theme, because it pops the FTP login info like my old install did. but I chown'd the wp directory to apache:apache. not sure what is up.
With WP issues, I often just untar a fresh install over top of the old one to make sure that there is no cruft.
-
@JaredBusch said:
Would it be possible to copy the boot partitions to the old drive and then try and attach it as the primary drive? That is more in depth CentOS than I know how to handle.
Possible but unlikely. That could be a lot of work to get working right.
-
So you just ended up nuking it?
-
Was easier really. Well would have been easier if the Wordpress export file had imported correctly..
-
Oh that sucks. What did it do on import?
-
@scottalanmiller said:
Oh that sucks. What did it do on import?
I posted in this thread.
http://wordpress.org/support/topic/import-process-only-displays-page-headerHere is my screenshot. Notice how the source code on the import page just stops dead mid page. there is obviously some kind of error in the plugin.
http://i.imgur.com/OMvVXPw.jpg -
Craptastic
-
Reinstalled everything from scratch and thought it was all good. But I am having a weird problem.
When I turn on any kind of permalink option other than the default it fails.
example: http://jaredbusch.com/?p=20 works.
If I change it to postname with date like I prefer, it gives me: The requested URL /2014/08/27/installing-owncloud-on-centos-7/ was not found on this server.But if you go to the landing page, it shows all three posts on the site.
-
but this site does not have that problem
-
Something is weird in this install.
Right after I reinstalled CentOS 7 and the various Wordpress sites, I was able to install plugins and run updates and such all from the built in processes.
Today I go to run install a new plugin on one of the domains and I get the FTP credentials screen. I know this means that Wordpress has no access to the folder/files it needs.
The directory was chown'd to apache:apache (and I did it again just now). What else can I look into? The only other ting I have seen is maybe my php process is not running as apache? But I am not sure how to check that.
-
I created test.php as follows
<?php echo 'Current script owner: ' . get_current_user(); ?> <br /> <?php phpinfo(); ?>
Then i chown apache:apache test.php to match the rest of the files in the folder.
[root@jaredweb daerma]# ls -l total 184 drwxr-xr-x. 3 apache apache 19 Aug 24 22:03 eq -rw-r--r--. 1 apache apache 418 Aug 24 14:02 index.php -rw-r--r--. 1 apache apache 19930 Aug 24 14:02 license.txt -rw-r--r--. 1 apache apache 7194 Aug 24 14:02 readme.html -rw-r--r--. 1 apache apache 88 Sep 1 10:40 test.php -rw-r--r--. 1 apache apache 4896 Aug 24 14:02 wp-activate.php drwxr-xr-x. 9 apache apache 4096 Aug 24 14:02 wp-admin -rw-r--r--. 1 apache apache 271 Aug 24 14:02 wp-blog-header.php -rw-r--r--. 1 apache apache 4818 Aug 24 14:02 wp-comments-post.php -rw-r--r--. 1 apache apache 3373 Aug 24 14:14 wp-config.php -rw-r--r--. 1 apache apache 3087 Aug 24 14:02 wp-config-sample.php drwxr-xr-x. 6 apache apache 77 Aug 24 15:07 wp-content -rw-r--r--. 1 apache apache 2932 Aug 24 14:02 wp-cron.php drwxr-xr-x. 12 apache apache 4096 Aug 24 14:02 wp-includes -rw-r--r--. 1 apache apache 2380 Aug 24 14:02 wp-links-opml.php -rw-r--r--. 1 apache apache 2359 Aug 24 14:02 wp-load.php -rw-r--r--. 1 apache apache 33407 Aug 24 14:02 wp-login.php -rw-r--r--. 1 apache apache 8235 Aug 24 14:02 wp-mail.php -rw-r--r--. 1 apache apache 11070 Aug 24 14:02 wp-settings.php -rw-r--r--. 1 apache apache 25665 Aug 24 14:02 wp-signup.php -rw-r--r--. 1 apache apache 4026 Aug 24 14:02 wp-trackback.php -rw-r--r--. 1 apache apache 3032 Aug 24 14:02 xmlrpc.php
then went to http://daerma.com/test.php (go ahead it is still there)
Everything looks right to me. -
Anyone have any other ideas on what maybe wrong with this wordpress install?
-
When you chowned, did you do it recursively?
chown -R apache:apache /webdir