27 Apr
2015
27 Apr
'15
6:48 p.m.
As ever, I'd quite like someone else to do the Wheezy to Jessie upgrade
first :)
The one thing I know I have to watch out for is that the change from
Apache 2.2 to 2.4 involves a change in the authentication modules for
websites that use it. I have it on \wp-admin for WordPress websites as
that stops the bots from bothering WordPress itself...
Ian
27 Apr
27 Apr
6:59 p.m.
Hi Ian,
On Mon, Apr 27, 2015 at 07:48:16PM +0100, Ian wrote:
As ever, I'd quite like someone else to do the
Wheezy to Jessie
upgrade first :)
People have been upgrading to jessie ever since shortly after wheezy
was released, since then Debian testing was what would become
jessie. But as usual, the problem is knowing if your exact
combination of packages has a hassle-free upgrade.
Are you asking if there's anyone who used apache 2.2 on wheezy with
authentication who has since upgraded to jessie with apache 2.4?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
28 Apr
28 Apr
1:48 a.m.
I went ahead and updated from wheezy to jessie. The update required an
additional 600MB, and I had to make some changes to my apache2 config. With
http://httpd.apache.org/docs/2.4/upgrading.html next to me, it was not too
much trouble. There's some changes in PHP as well which I'll have to look
into before upgrading another VPS.
--
Cheers,
Frederik Vanrenterghem
2015-04-28 2:59 GMT+08:00 Andy Smith <andy(a)bitfolk.com>om>:
Hi Ian,
On Mon, Apr 27, 2015 at 07:48:16PM +0100, Ian wrote:
As ever, I'd quite like someone else to do
the Wheezy to Jessie
upgrade first :)
People have been upgrading to jessie ever since shortly after wheezy
was released, since then Debian testing was what would become
jessie. But as usual, the problem is knowing if your exact
combination of packages has a hassle-free upgrade.
Are you asking if there's anyone who used apache 2.2 on wheezy with
authentication who has since upgraded to jessie with apache 2.4?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAlU+hv8ACgkQIJm2TL8VSQsxxQCeMEjBreDNp0M9Bhdsy8OadmKI
WqQAnRsN+XUg83IyTMY9e5gcVErVZ9Lr
=xkOi
-----END PGP SIGNATURE-----
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
2:36 a.m.
I upgraded my computers here at home on Sunday. Met a couple of minor
hitches which won't be relevant to the VPS. Am reading about the Apache
thing now ready to do the big upgrade this week - hopefully.
On 28 April 2015 at 02:48, Frederik Vanrenterghem <
frederik(a)vanrenterghem.biz> wrote:
I went ahead and updated from wheezy to jessie. The
update required an
additional 600MB, and I had to make some changes to my apache2 config. With
http://httpd.apache.org/docs/2.4/upgrading.html next to me, it was not
too much trouble. There's some changes in PHP as well which I'll have to
look into before upgrading another VPS.
--
Cheers,
Frederik Vanrenterghem
2015-04-28 2:59 GMT+08:00 Andy Smith <andy(a)bitfolk.com>om>:
--
Keith Williams
คืนใดมืดที่สุด จะเห็นดาวชัดที่สุด
Wondrous Thai http://www.wondrousthai.com
FCLT magazine http://issuu.com/fcltmagazine/docs/fclt_september_2014_issue_1
Farang Can Learn Thai www.farangcanlearnthai.com
Keith's Place www.keiths-place.co.uk
Tailor Made English www.tmenglish.org
West Norfolk RSPCA www.westnorfolkrspca.org.uk
Hi Ian,
On Mon, Apr 27, 2015 at 07:48:16PM +0100, Ian wrote:
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
As ever, I'd quite like someone else to do
the Wheezy to Jessie
upgrade first :)
People have been upgrading to jessie ever since shortly after wheezy
was released, since then Debian testing was what would become
jessie. But as usual, the problem is knowing if your exact
combination of packages has a hassle-free upgrade.
Are you asking if there's anyone who used apache 2.2 on wheezy with
authentication who has since upgraded to jessie with apache 2.4?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAlU+hv8ACgkQIJm2TL8VSQsxxQCeMEjBreDNp0M9Bhdsy8OadmKI
WqQAnRsN+XUg83IyTMY9e5gcVErVZ9Lr
=xkOi
-----END PGP SIGNATURE-----
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
2:26 p.m.
Well, I did it! Wheezy to Jessie on one of my VPS today. It is one with
just a couple of websites that are really just testbeds and a mailserver.
(Postfix/Dovecot) Having backed up all the mail server config. and the
sites and mysql, I decided to just give it a go. A rough outline:-
Backups
Update all wheezy packages and autoremove, autoclean etc
Change sources.list then upgrade
OpenVPN and clamav-daemon had problems so I purged them and reinstalled
Otherwise it was plain sailing.
Finally Xen shell shutdown and boot
The apache config files needed some rewriting. A lot of the directives are
moved from virtual host files to the main apache2.conf and you have to make
sure that virtualhost config files are named .conf - all summarised here:
https://www.digitalocean.com/community/tutorials/migrating-your-apache-conf…
One other point, if you are signing in as root and using password instead
of key, the Jessie upgrade changes the default SSH config to
rootpasswordlogin no
Keith
On 28 April 2015 at 03:36, Keith Williams <keithwilliamsnp(a)gmail.com> wrote:
I upgraded my computers here at home on Sunday. Met a
couple of minor
hitches which won't be relevant to the VPS. Am reading about the Apache
thing now ready to do the big upgrade this week - hopefully.
On 28 April 2015 at 02:48, Frederik Vanrenterghem <
frederik(a)vanrenterghem.biz> wrote:
--
Keith Williams
คืนใดมืดที่สุด จะเห็นดาวชัดที่สุด
Wondrous Thai http://www.wondrousthai.com
FCLT magazine http://issuu.com/fcltmagazine/docs/fclt_september_2014_issue_1
Farang Can Learn Thai www.farangcanlearnthai.com
Keith's Place www.keiths-place.co.uk
Tailor Made English www.tmenglish.org
West Norfolk RSPCA www.westnorfolkrspca.org.uk
I went ahead and updated from wheezy to jessie.
The update required an
additional 600MB, and I had to make some changes to my apache2 config. With
http://httpd.apache.org/docs/2.4/upgrading.html next to me, it was not
too much trouble. There's some changes in PHP as well which I'll have to
look into before upgrading another VPS.
--
Cheers,
Frederik Vanrenterghem
2015-04-28 2:59 GMT+08:00 Andy Smith <andy(a)bitfolk.com>om>:
--
Keith Williams
คืนใดมืดที่สุด จะเห็นดาวชัดที่สุด
Wondrous Thai http://www.wondrousthai.com
FCLT magazine
http://issuu.com/fcltmagazine/docs/fclt_september_2014_issue_1
Farang Can Learn Thai www.farangcanlearnthai.com
Keith's Place www.keiths-place.co.uk
Tailor Made English www.tmenglish.org
West Norfolk RSPCA www.westnorfolkrspca.org.uk
Hi Ian,
On Mon, Apr 27, 2015 at 07:48:16PM +0100, Ian wrote:
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
As ever, I'd quite like someone else to do
the Wheezy to Jessie
upgrade first :)
People have been upgrading to jessie ever since shortly after wheezy
was released, since then Debian testing was what would become
jessie. But as usual, the problem is knowing if your exact
combination of packages has a hassle-free upgrade.
Are you asking if there's anyone who used apache 2.2 on wheezy with
authentication who has since upgraded to jessie with apache 2.4?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAlU+hv8ACgkQIJm2TL8VSQsxxQCeMEjBreDNp0M9Bhdsy8OadmKI
WqQAnRsN+XUg83IyTMY9e5gcVErVZ9Lr
=xkOi
-----END PGP SIGNATURE-----
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
4:13 p.m.
On Mon, Apr 27, 2015 at 07:48:16PM +0100, Ian wrote:
As ever, I'd quite like someone else to do the
Wheezy to Jessie
upgrade first :)
The one thing I know I have to watch out for is that the change from
Apache 2.2 to 2.4 involves a change in the authentication modules
for websites that use it. I have it on \wp-admin for WordPress
websites as that stops the bots from bothering WordPress itself...
There's nothing stopping you from (and I think its sensible to)
installing Apache 2.4 from source in /usr/local/, copying your conf, and
changing the port and log/pid file locations to slight variations so
that you can test Apache before doing a switch over. Slight issues
arise from .htaccess locations, so copy your web tree to a second path.
Since it's wordpress most of the real content will be in a DB that you
don't need to worry about.
Once you've got that working you could use something like this after
doing the upgrade. Though, there are times that its good to manage your
own Apache config, or maybe install nginx first and have that proxy the
heavy lifting through to Apache and let nginx serve images...
# find . -name .htaccess | tar cvf - -T - \
| ( cd /current_apache_path && tar xvf - )
Then if you're going to use nginx you can run PHP as FastCGI which some
may argue is better...
Well done biting the bullet and doing the upgrade, at least you have a
test system, and also well done for doing a backup first :)
--
Best regards,
Ed http://www.s5h.net/
4:44 p.m.
On Mon, Apr 27, 2015 at 07:48:16PM +0100, Ian wrote:
As ever, I'd quite like someone else to do the
Wheezy to Jessie
upgrade first :)
The one thing I know I have to watch out for is that the change from
Apache 2.2 to 2.4 involves a change in the authentication modules
for websites that use it. I have it on \wp-admin for WordPress
websites as that stops the bots from bothering WordPress itself...
I've had no trouble on a couple of desktops, I haven't dared do my
bitfolk VPS yet.
I did find doing:
dpkg-reconfigure fontconfig-config
and making sure hinting was enabled helped fonts-wise.
Michael
3286
days inactive
3287
days old
6 comments
6 participants
participants (6)
-
Andy Smith -
ed -
Frederik Vanrenterghem -
Ian -
Keith Williams -
Michael Stevens