User:Woozle/Redmine/1 - Revision history

Woozle: Woozle moved page User:Woozle/Redmine to User:Woozle/Redmine/1 without leaving a redirect: to keep it separate from this year's attempt

2020-02-09T13:39:22Z

Woozle moved page User:Woozle/Redmine to User:Woozle/Redmine/1 without leaving a redirect: to keep it separate from this year's attempt

← Older revision	Revision as of 13:39, 9 February 2020
(No difference)

Woozle: /* part 2 (success) */ tidying up

2018-01-06T18:56:41Z

part 2 (success): tidying up

← Older revision		Revision as of 18:56, 6 January 2018
Line 351:		Line 351:

	After making that change and doing <code>service apache2 reload</code>, Redmine gives me a log-in screen. I log in and everything seems to be working (and it's version 3.2.1.stable now).		After making that change and doing <code>service apache2 reload</code>, Redmine gives me a log-in screen. I log in and everything seems to be working (and it's version 3.2.1.stable now).
			===part 3 (tidying up)===
			A couple of folders weren't write-accessible by Redmine, so I changed ownership to vbz-net:
			:<code>chown -R vbz-net:vbz-net /var/lib/redmine/default</code>
			:<code>chown -R vbz-net:vbz-net /usr/share/redmine/public/plugin_assets/</code>

			Probably both of these folders -- <code>/var/lib/redmine/default</code> and <code>/usr/share/redmine/public/</code> -- should be inside <code>/home/vbz-net/</code> or even <code>/home/vbz-net/domains/rm.vbz.net</code>. I'll fix that when I have time to re-research how to modify Redmine's config so it knows to look for them in the appropriate spots.

Woozle: section reorg

2018-01-06T18:43:35Z

section reorg

← Older revision		Revision as of 18:43, 6 January 2018
Line 282:		Line 282:
	</pre>		</pre>
	At least we're back to Apache being happy. (Yes, I keep testing other sites on the same server to make sure they are still working.)		At least we're back to Apache being happy. (Yes, I keep testing other sites on the same server to make sure they are still working.)
	===part ~~4 (Jan. 6)~~===		==2018-01-06==
			===part 1===
	Somewhere along the line, I enabled an option to show the error message on the web page. The key part of the error message is this:		Somewhere along the line, I enabled an option to show the error message on the web page. The key part of the error message is this:
	[!] There was an error parsing `Gemfile`: Permission denied @ rb_sysopen - config/database.yml. Bundler cannot continue.		[!] There was an error parsing `Gemfile`: Permission denied @ rb_sysopen - config/database.yml. Bundler cannot continue.
Line 344:		Line 345:

	That seems to be all for actually installing Passenger, so maybe the problem is with the [https://www.phusionpassenger.com/library/walkthroughs/deploy/ruby/digital_ocean/apache/oss/xenial/deploy_app.html (Redmine) app] configuration...		That seems to be all for actually installing Passenger, so maybe the problem is with the [https://www.phusionpassenger.com/library/walkthroughs/deploy/ruby/digital_ocean/apache/oss/xenial/deploy_app.html (Redmine) app] configuration...
	===~~and finally~~===		===part 2 (success)===
	It [https://toot.cat/@woozle/4163652 turns out] the key piece was to add the following to the virtual domain config in Apache:		It [https://toot.cat/@woozle/4163652 turns out] the key piece was to add the following to the virtual domain config in Apache:
	:<code>PassengerUser vbz-net</code>		:<code>PassengerUser vbz-net</code>

Woozle: /* part 4 (Jan. 6) */ finally

2018-01-06T18:42:01Z

part 4 (Jan. 6): finally

← Older revision		Revision as of 18:42, 6 January 2018
Line 344:		Line 344:

	That seems to be all for actually installing Passenger, so maybe the problem is with the [https://www.phusionpassenger.com/library/walkthroughs/deploy/ruby/digital_ocean/apache/oss/xenial/deploy_app.html (Redmine) app] configuration...		That seems to be all for actually installing Passenger, so maybe the problem is with the [https://www.phusionpassenger.com/library/walkthroughs/deploy/ruby/digital_ocean/apache/oss/xenial/deploy_app.html (Redmine) app] configuration...
			===and finally===
			It [https://toot.cat/@woozle/4163652 turns out] the key piece was to add the following to the virtual domain config in Apache:
			:<code>PassengerUser vbz-net</code>
			The reference page for this is [https://www.phusionpassenger.com/library/config/apache/reference/#passengerstartupfile here], with some additional explanation [https://www.phusionpassenger.com/library/deploy/apache/user_sandboxing.html#how-it-works here].

			After making that change and doing <code>service apache2 reload</code>, Redmine gives me a log-in screen. I log in and everything seems to be working (and it's version 3.2.1.stable now).

Woozle: /* part 3 */ part 4

2018-01-06T15:39:42Z

part 3: part 4

@@ Line 278: / Line 278: @@
 To activate the new configuration, you need to run:
    service apache2 restart
-root@cloud4:~# service apache2 restart
+root@cloud4:~# service apapart 4che2 restart
 root@cloud4:~#
 </pre>
 At least we're back to Apache being happy. (Yes, I keep testing other sites on the same server to make sure they are still working.)

Woozle: /* part 2 */ part 3

2018-01-05T00:05:59Z

part 2: part 3

← Older revision		Revision as of 00:05, 5 January 2018
Line 175:		Line 175:

	So then the next step was to muck around with Apache's config to point it to Redmine and make it go. There were a couple of Rails directives that Apache didn't recognize and which were causing the reload to fail with no error. [https://cutie.space/users/iona/statuses/99292704349862209 Apparently] "libapache2-mod-passenger" needs to be installed.		So then the next step was to muck around with Apache's config to point it to Redmine and make it go. There were a couple of Rails directives that Apache didn't recognize and which were causing the reload to fail with no error. [https://cutie.space/users/iona/statuses/99292704349862209 Apparently] "libapache2-mod-passenger" needs to be installed.
			===part 3===
			Installed that, restored the missing Rails directives, reloaded Apache... and now I get a Rails error page, which is progress. Following it through, I end up doing this:
			<pre>
			root@cloud4:~# passenger-config --detect-apache2
			Looking for possible Apache installations...
			--> Looking for /usr/local/sbin/apxs2: not found
			--> Looking for /usr/local/bin/apxs2: not found
			--> Looking for /usr/sbin/apxs2: not found
			--> Looking for /usr/bin/apxs2: not found
			--> Looking for /sbin/apxs2: not found
			--> Looking for /bin/apxs2: not found
			--> Looking for /usr/games/apxs2: not found
			--> Looking for /usr/local/games/apxs2: not found
			--> Looking for /snap/bin/apxs2: not found
			--> Looking for /usr/local/sbin/apxs: not found
			--> Looking for /usr/local/bin/apxs: not found
			--> Looking for /usr/sbin/apxs: not found
			--> Looking for /usr/bin/apxs: not found
			--> Looking for /sbin/apxs: not found
			--> Looking for /bin/apxs: not found
			--> Looking for /usr/games/apxs: not found
			--> Looking for /usr/local/games/apxs: not found
			--> Looking for /snap/bin/apxs: not found
			--> Looking for : found

			Analyzing ...
			Detecting main Apache executable...
			Detecting version...
			--> 2.4.18
			Detecting control command...
			Cannot find a usable Apache installation using .

			Final autodetection results
			Sorry, this program cannot find an Apache installation.

			Please install Apache and its development headers.

			* To install Apache:
			Please install it with apt-get install apache2-mpm-worker

			* To install Apache development headers:
			Please install it with apt-get install apache2-threaded-dev

			If you are sure that you have Apache installed, please read the documentation:
			https://www.phusionpassenger.com/library/install/apache/customizing_compilation_process.html#forcing-location-of-command-line-tools-and-dependencies
			root@cloud4:~# apt install apache2-mpm-worker
			Reading package lists... Done
			Building dependency tree
			Reading state information... Done
			E: Unable to locate package apache2-mpm-worker
			root@cloud4:~#
			</pre>
			The instructions are misleading. <code>apache2-mpm-worker</code> is actually the "[https://httpd.apache.org/docs/2.4/mod/worker.html worker]" module already installed with Apache; it just needs to be activated.

			Following instructions [https://askubuntu.com/questions/524770/apache-enable-worker-mpm here]:
			<pre>
			root@cloud4:~# a2dismod mpm_prefork
			Module mpm_prefork disabled.
			To activate the new configuration, you need to run:
			service apache2 restart
			root@cloud4:~# a2enmod mpm_worker
			Considering conflict mpm_event for mpm_worker:
			Considering conflict mpm_prefork for mpm_worker:
			Enabling module mpm_worker.
			To activate the new configuration, you need to run:
			service apache2 restart
			</pre>
			The instructions then say to run the following command to see if it's working -- but they didn't say to restart Apache first, so I didn't:
			<pre>
			root@cloud4:~# apachectl -V \| grep -i mpm
			[Fri Jan 05 00:00:19.913519 2018] [so:warn] [pid 21156] AH01574: module dav_module is already loaded, skipping
			[Fri Jan 05 00:00:19.952379 2018] [:crit] [pid 21156:tid 140326418311040] Apache is running a threaded MPM, but your PHP Module is not compiled to be threadsafe. You need to recompile PHP.
			AH00013: Pre-configuration failed
			</pre>
			The instructions say if you get that message, then do this:
			<pre>
			root@cloud4:~# apt remove libapache2-mod-php5
			Reading package lists... Done
			Building dependency tree
			Reading state information... Done
			Package 'libapache2-mod-php5' is not installed, so not removed
			The following package was automatically installed and is no longer required:
			libllvm4.0
			Use 'apt autoremove' to remove it.
			0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
			</pre>
			Well, okay, seems that package is already removed. Maybe I just needed to go ahead and restart Apache?
			<pre>
			root@cloud4:~# service apache2 restart
			Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
			</pre>
			So, we're back there again. Okay, time to revert and consider other options.
			<pre>
			root@cloud4:~# a2dismod mpm_worker
			Module mpm_worker disabled.
			To activate the new configuration, you need to run:
			service apache2 restart
			root@cloud4:~# a2enmod mpm_prefork
			Considering conflict mpm_event for mpm_prefork:
			Considering conflict mpm_worker for mpm_prefork:
			Enabling module mpm_prefork.
			To activate the new configuration, you need to run:
			service apache2 restart
			root@cloud4:~# service apache2 restart
			root@cloud4:~#
			</pre>
			At least we're back to Apache being happy. (Yes, I keep testing other sites on the same server to make sure they are still working.)

Woozle: saving work

2018-01-04T17:23:45Z

saving work

← Older revision		Revision as of 17:23, 4 January 2018
Line 33:		Line 33:
	(Now I need to go migrate the data.)		(Now I need to go migrate the data.)
	==2018-01-04==		==2018-01-04==
			===part 1===
	* Data migrated to vbz-rm on cloud4.		* Data migrated to vbz-rm on cloud4.
	* Created MySQL user, gave it ALL privileges on vbz-rm.		* Created MySQL user, gave it ALL privileges on vbz-rm.
Line 166:		Line 167:

	So now where are we? I guess I need to point test.rm.vbz.net at cloud4, and tell Apache that this is an alias for Redmine, so I can test this deployment without making the old one inaccessible... or is there an upgrade process which needs to be run from the CLI? Will have to check on that.		So now where are we? I guess I need to point test.rm.vbz.net at cloud4, and tell Apache that this is an alias for Redmine, so I can test this deployment without making the old one inaccessible... or is there an upgrade process which needs to be run from the CLI? Will have to check on that.
			===part 2===
			Finding definitive upgrade instructions for Redmine has not been fruitful; so far, [http://www.redmine.org/projects/redmine/wiki/HowTo_Migrate_Redmine_to_a_new_server_to_a_new_Redmine_version this] is the only thing I've been able to find, and it's for an old version and doesn't explain a lot of things.

			Based on that, though, I tried this:
			root@cloud4:/usr/share/redmine# rake db:migrate RAILS_ENV=production
			...but nothing happened, which could mean either success or failure or "nothing needed doing".

			So then the next step was to muck around with Apache's config to point it to Redmine and make it go. There were a couple of Rails directives that Apache didn't recognize and which were causing the reload to fail with no error. [https://cutie.space/users/iona/statuses/99292704349862209 Apparently] "libapache2-mod-passenger" needs to be installed.

Woozle at 13:27, 4 January 2018

2018-01-04T13:27:33Z

Show changes

Woozle: another note

2017-12-28T10:04:46Z

another note

← Older revision		Revision as of 10:04, 28 December 2017
Line 27:		Line 27:
	...which I assume is the result of me saying "no", and not an actual error.		...which I assume is the result of me saying "no", and not an actual error.

	~~Nobody~~ seemed to be forthcoming with information about where file uploads are stored (so they can be migrated to a new server), so I figured it out the hard way by looking in the "attachments" table for a filename, and then searching the hard drive for that file. Apparently they are stored in '''/var/lib/redmine/default/files'''.		Apparently this also installs redmine itself, as "apt install redmine" comes back with nothing new to install.

			No sources seemed to be forthcoming with information about where file uploads are stored (so they can be migrated to a new server), so I figured it out the hard way by looking in the "attachments" table for a filename, and then searching the hard drive for that file. Apparently they are stored in '''/var/lib/redmine/default/files'''.

	(Now I need to go migrate the data.)		(Now I need to go migrate the data.)

Woozle: file location

2017-12-27T23:57:06Z

file location

← Older revision		Revision as of 23:57, 27 December 2017
Line 26:		Line 26:
	</pre>		</pre>
	...which I assume is the result of me saying "no", and not an actual error.		...which I assume is the result of me saying "no", and not an actual error.

			Nobody seemed to be forthcoming with information about where file uploads are stored (so they can be migrated to a new server), so I figured it out the hard way by looking in the "attachments" table for a filename, and then searching the hard drive for that file. Apparently they are stored in '''/var/lib/redmine/default/files'''.

	(Now I need to go migrate the data.)		(Now I need to go migrate the data.)