Hide Forgot
Working with lorax-25.16-1 on a Fedora 25 x86_64 KVM virtual machine and trying to use livemedia-creator as documented here: https://fedoraproject.org/wiki/Livemedia-creator-_How_to_create_and_use_a_Live_CD It was working for me with the previous lorax release but the update to lorax-25.16-1, the anaconda server starts but it can never connect to it. I have tried several times over several reboots and still the same thing on two different build systems that were previously working. - - - - - Here's what my command line looks like: setenforce 0 livemedia-creator \ --no-virt \ --ks /root/livemedia-creator/MontanaLinux/MontanaLinux-F25-x86_64.ks \ --project MontanaLinux \ --title MontanaLinux \ --releasever 25 \ --iso-only \ --make-iso \ --volid MontanaLinux-F25-x86_64 \ --logfile=/root/livemedia-creator/livemedia.log \ --iso-name MontanaLinux-F25-054-x86_64.iso - - - - - Here's the output from the run: /usr/lib64/python3.5/optparse.py:999: PendingDeprecationWarning: The KSOption class is deprecated and will be removed in pykickstart-3. Use the argparse module instead. option = self.option_class(*args, **kwargs) 2016-10-28 08:59:24,572: disk_img = /var/tmp/lmc-disk-nnbr49z2.img 2016-10-28 08:59:24,572: Using disk size of 11242MiB 2016-10-28 08:59:26,599: Running anaconda. 2016-10-28 08:59:41,385: Processing logs from ('127.0.0.1', 44640) 2016-10-28 08:59:42,302: Starting installer, one moment... 2016-10-28 08:59:42,302: terminal size detection failed, using default width 2016-10-28 08:59:42,302: anaconda 25.20.5-1 for MontanaLinux 25 (pre-release) started. 2016-10-28 09:00:01,480: Starting automated install................... 2016-10-28 09:00:01,481: ================================================================================ 2016-10-28 09:00:01,481: ================================================================================ 2016-10-28 09:00:01,481: Installation 2016-10-28 09:00:01,481: 2016-10-28 09:00:01,482: 1) [x] Language settings 2) [x] Time settings 2016-10-28 09:00:01,482: (English (United States)) (US/Mountain timezone) 2016-10-28 09:00:01,482: 3) [x] Installation source 4) [x] Software selection 2016-10-28 09:00:01,482: (http://img.cs.montana.edu/linu (Custom software selected) 2016-10-28 09:00:01,482: x/fedora/development/25/Everyth 2016-10-28 09:00:01,483: ing/x86_64/os/) 2016-10-28 09:00:01,483: 5) [x] Network configuration 2016-10-28 09:00:01,483: (Wired (ens3) connected) 2016-10-28 09:00:01,483: ================================================================================ 2016-10-28 09:00:01,484: ================================================================================ 2016-10-28 09:00:01,484: Progress 2016-10-28 09:00:01,484: Setting up the installation environment 2016-10-28 09:00:02,082: . 2016-10-28 09:00:02,082: Running pre-installation scripts 2016-10-28 09:00:04,721: . 2016-10-28 09:00:04,721: Starting package installation process 2016-10-28 09:00:04,903: Unable to init server: Could not connect: Connection refused 2016-10-28 09:00:04,956: Unable to init server: Could not connect: Connection refused 2016-10-28 09:00:04,957: Unable to init server: Could not connect: Connection refused 2016-10-28 09:00:05,230: Running anaconda failed: process '['anaconda', '--kickstart', '/root/livemedia-creator/MontanaLinux/MontanaLinux-F25-x86_64.ks', '--cmdline', '--dirinstall', '--remotelog', '127.0.0.1:56489']' exited with status 1 2016-10-28 09:00:05,231: Shutting down log processing 2016-10-28 09:00:05,565: Install failed: novirt_install failed 2016-10-28 09:00:05,565: Removing bad disk image 2016-10-28 09:00:05,581: ERROR: Image creation failed: novirt_install failed - - - - - I have turned off firewalld.service on the build host (although I thought 127.0.0.1 was a trusted device and connections wouldn't be denied) but that hasn't helped. - - - - - I can provide my kickstart file if needed... but I assume this error is reproducable by others. If not, please let me know.
That error, IIRC, usually comes from anaconda's error handling (python-meh, abrt) trying to open a window to tell you about a traceback. Check the other logs for errors -- especially scriptlet problems which Anaconda 25 changed to be fatal. The logs from anaconda should be in ./anaconda/ or /tmp/ if something went wrong with copying them. And just to be clear, when you say it was working fine, was that with lorax-25.x? Or a previous release?
Found anaconda error log... and sure enough... two of the packages I had in my package list had disappeared (system-config-date and xorg-x11-drv-vmmouse) were no longer available. Removed those and it is progressing... and no longer giving me a connect issue. Now that I know to check the anaconda log (I had looked at the program.log livemedia.log and found no errors to speak of), I should fair better.