I finally got around to upgrading from Fedora25 to Fedora26.
The layout is I have two partitions of which at any time one of the is
the root partition, which contains everything but the /boot partition,
and the other is not used. I have a separate /boot partition. When I
upgrade I go into single user and duplicate the currently used root
partition to the unused one using:
# mkfs.xfs /dev/fedora/rootb
# mount /dev/fedora/rootb /mnt
# xfsdump -J - / | xfsrestore -J - /mnt
Then I modify /boot/grub2/grub.cfg and tell vmlinuz to use the new
partition and modify /mnt/etc/fstab to have the root partition be the
new partition. I then reboot and indeed I come up on the new partition
just fine, still running F25. On this new partition I do the OS upgrade.
The upgrade goes fine and it boots up just fine on Fedora26.
I did a search for .rpmsave files to see if the upgrade changed any
configuration files I may have modified locally and that came up empty.
However, when I try and use the application that runs on that machine
which is PHP SOAP I get an error "can not connect to host". The nslookup
for that host is correct and I can ping the host. As far as I know
nothing has changed on that host. My code uses the following to handle
self-signed certs:
'stream_context'=> stream_context_create(array('ssl'=>
array('verify_peer'=>false,'verify_peer_name'=>false)))
But I know that the cert on the host I am contacting is not self-signed.
If I go back and edit /boot/grub2/grub.cfg to boot up off the old
Fedora25 root partition it comes up fine and I can use the application
just fine to connect to the host.
Is there any history of PHP or SOAP having a change from F25 to F26 that
could explain the "can not connect to host" error I am seeing on F26
that I don't see on F25 ?
Thanks
Chris Kottaridis
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
