wiki/amazon-ec2.md
... ...
@@ -352,19 +352,19 @@ Follow these steps to upgrade the AMI:
352 352
353 353
### ELB Setup with replication server(s)
354 354
- Remove all Replica's from the ELB and wait at least 2 minutes until no request reaches their Apache webservers anymore. You can check this with looking at `apachetop` on the respective instances. Let only the Master server live inside the ELB.
355
-- Login to each instance as `sailing`-user and stop the java instance with `~/servers/server/stop;`
356
-- As soon as the instance is successfully stopped (verify with `ps -ef |grep "java"`) copy all sailing logs towards `/var/log/old/<event-name>/<instance-public-ipv4/` with following command
355
+- Login to each server instance as `root`-user and stop the java instance with `/home/sailing/servers/server/stop;`
356
+- As soon as the instance is successfully stopped (verify with `ps -ef | grep "java"`) copy all server logs towards `/var/log/old/<event-name>/<instance-public-ipv4/` with following command
357 357
```
358
-cp -rf ~/servers/server/logs/* /var/log/old/<event-name>/<instance-public-ipv4>/
358
+cp -rf /home/sailing/servers/server/logs/* /var/log/old/<event-name>/<instance-public-ipv4>/
359 359
```
360 360
- Once this is done, make sure all HTTP logs are also copied to the above location
361 361
- Either you wait now for the next day, then the http logrotate script ran through
362 362
- Or you manually force a logrotate run with `logrotate --force /etc/logrotate.d/httpd`, which copies `/var/log/httpd/` towards `/var/log/old/<event-name>/<instance-public-ipv4>`
363
-- Please verify that there are no left open queues on RabbitMQ for that particular replication server. In case purge the queue of this replica.
364
-- Once all replica's are terminated and you have only running the Master server inside the ELB, go ahead with a master data import on sapsailing.com for the event, grabbing the data from you Master server
365
-- Once MDI is done, make sure you track the corresponding races (be careful to also track the smartphone tracked regattas!)
366
-- Once this is done, remember to remove any entries on sapsailing.com regarding "remote sailing instances", otherwise the event will appear two times on public events list
367
-- On the same time, you will need to modify or add an entry on the central Apache server to point the event URL towards the Archive server. And remove your `-master` Event URL, as you don't need this one anymore
363
+- Please verify that there are no open queues left on RabbitMQ for that particular replication server. In case purge the queue of this replica.
364
+- Once all replica's are terminated and only the Master server is running inside the ELB, go ahead with a master data import on sapsailing.com for the event, grabbing the data from your master server
365
+- Once the master data import is done, make sure you track the corresponding races (be careful to also track the smartphone tracked regattas)
366
+- Once this is done, remember to remove any entries on sapsailing.com regarding "remote sailing instances", otherwise the event will appear two times on the public events list
367
+- at the same time, you need to modify or add an entry on the central Apache server to point the event URL towards the Archive server. Make sure you have removed the `-master` event URL, as you don't need this one anymore
368 368
```
369 369
# <EVENT> <YEAR>
370 370
Use Event-ARCHIVE-SSL-Redirect <EVENT><YEAR>.sapsailing.com "<EVENT-UUID>"