Wordpress network/multisite on AWS micro instance

I’ve found BitNami only earlier this week and it’s really a great tool!

But I’ve had a weird problem with the Wordpress ami. Since I’m a newbie I’m using BitNami’s cloud service on a micro instance at AWS/ec2.

The initial run was perfect. The server came up beautifully, I configured the network according to http://codex.wordpress.org/Create_A_Network. Everything worked flawlessly: updating to wp 3.2, installing a couple of themes, plugins, creating 2 sites, making some posts etc.

Being new to BitNami’s cloud service I experimented a little and I ran into a rather big problem.

When I stop and restart the server, the module (at …/wordpress ) would either give a 404 error or not respond with the server’s memory usage is at 99%.

After some testing, I think the network activation is the breaking point. When I create a wordpress network, the server does not survive a reboot or start/stop — all other modifications could be done without breaking at reboot.

Has anybody else encountered this? Is it just not feasible to run a network in a micro instance (and if so why does it only break after a reboot?)

I’m not sure I understand you correctly. Bitnami’s updateip-tool seems to work correctly, i.e., wp-config.php shows the correct DOMAIN_CURRENT_SITE. I haven’t changed the url manually — I’m just running tests so far.

I really think the problem is caused by wp network/multisite. If I don’t activate network/multisite, everything is fine — stop/starting the instance does not cause any problems.

After network/multisite is activated, the instance still runs fine at first. But after one restart (or start/stop), the instance breaks: When starting the instance everything looks fine (e.g. /applications.html works), but as soon as I try to go to /wordpress, the server just does not respond — and the server’s memory usage goes to 99%.

Maybe somebody could try to reproduce this. Anyway, any ideas are appreciated!

Update. I have failed to reproduce this so far today. I have restarted the instance after each step (update to wp3.2, creating a network, adding 2 sites, adding MathJax plugin) and yet nothing stopped working. (I also noticed that a working micro instance has 99% memory use so that’s not the problem, I guess)

So that’s good news, but I’m a little bit worried because I don’t understand what caused the problems yesterday. I guess I need to experiment more before I trust BitNami+AWS with a non-test run. (and I guess I need to figure out how the different backup solutions work…)

@Beltrán I’m really sorry. It seems you were right from the start. Could it be that the updateip-tool doesn’t always work? Running it manually does not work either.

So I changed the wp-config — and get a database-connection error (as expected). But changing the mysql entry using your link does not work because I don’t know the password. I’m sure it’s somewhere in the forum but I can’t find anything…