Re: [PVE-User] sbin/unconfigured.sh

[Steve]

​​
Here is final grub4dos menu for use with Easy2Boot which works

iftitle [if exist $HOME$/proxmox-ve_4.4-eb2d6f1e-2.iso] proxmox 4.4\n You
must enter the correct USB name.
set ISO=proxmox-ve_4.4-eb2d6f1e-2.iso

set ldisk=
errorcheck off
if not exist ldisk geometry (hd9) > nul && set ldisk=sdj4
if not exist ldisk geometry (hd8) > nul && set ldisk=sdi4
if not exist ldisk geometry (hd7) > nul && set ldisk=sdh4
if not exist ldisk geometry (hd6) > nul && set ldisk=sdg4
if not exist ldisk geometry (hd5) > nul && set ldisk=sdf4
if not exist ldisk geometry (hd4) > nul && set ldisk=sde4
if not exist ldisk geometry (hd3) > nul && set ldisk=sdd4
if not exist ldisk geometry (hd2) > nul && set ldisk=sdc4
if not exist ldisk geometry (hd1) > nul && set ldisk=sdb4

echo
echo -e $[0104] I guess partition 4 of the USB drive will be %ldisk%
echo
set /p ldisk=Enter linux device name for USB drive (ptn4), e.g. sdb4 or
sdc4 (ESC=%ldisk%) :
echo
pause --wait=3 Will use /dev/%ldisk%
set NOSUG=1
set redir=> nul
/%grub%/QRUN.g4b $HOME$/%ISO%
kernel /boot/linux26 ro ramdisk_size=16777216 lvm2root=/dev/%ldisk% vga=791
rw
initrd /boot/initrd.img
boot

Thanks for your help
​.​
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Steve]

One last hurdle!

instead of /dev/sda1  I want to use /dev/disk/by-uuid/XXX because I
don't know how many disks there are in the system

but it does not work - I presume that /dev/disk/by-uuid does not yet exist
at the time the init script is running?

Is there any other way to reference the partition? I am guessing that
by-label will not work either?...

Steve



On 19 May 2017 at 10:04, Fabian Grünbichler 
wrote:

> On Fri, May 19, 2017 at 09:40:54AM +0100, Steve wrote:
> > I tried proxdebug. No extra messages are generated after the network has
> > initialised.
> > There is no log in /tmp folder ? Has the log moved?
> >
> > How do I run xinit? Where is it?
> > Do you mean init? If I run this it says must be run as PID 1 - how can I
> > fix this (sorry, I am not a linux guru!)
> >
>
> just type "xinit" in the debug shell. but if you are not comfortable
> with this kind of debugging, you might be better off just (temporarily)
> "sacrificing" a thumb drive for the PVE installer instead of trying to
> get this non-standard way to boot it to work ;)
>
> I hope to fix the initrd during the 5.x release cycleto to allow booting
> in some kind of loopback mode, but it's a low priority item on my todo
> list..
>
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Any way to patch / force proxmox to support /etc/network/interfaces.d/*?

[Brian :]

you could probably cat /etc/network/interfaces.d/* >
/etc/network/interfaces as a horrible hack.


On Fri, May 19, 2017 at 1:03 PM, Eugen Mayer  wrote:
> Hallo,
>
> due to the nature of deploying with chef and configuring my network, 
> interfaces, bridges there, entries in /etc/network/interfaces.d/eth0 .. 
> /etc/network/interfaces.d/vmbr0 are created.
> The issue no is, that /etc/network/interfaces basically just includes
>
> source /etc/network/interfaces.d/*
>
> and is empty. Proxmox does not support that, does not list me any interfaces 
> in the UI and does not let me assign my KVM VM to any interface. Any way i 
> could patch that / force that / give proxmox a static list of interfaces ?
>
> Thanks
>
> --
> Eugen
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Steve]

I think the problem is with grub4dos.

If I use this menu from a FAT32 USB drive

title ProxMox lvm2root=sda1
kernel /boot/linux26 ro ramdisk_size=16777216 lvm2root=/dev/sda1 rw quiet
splash=silent
initrd /boot/initrd.img

then it does not work and I get the Installation aborted message

but if I use the same menu in grub2 from the same drive,

menuentry 'Install Proxmox VE sda1' --class debian --class gnu-linux
--class gnu --class os {
linux /boot/linux26 ro ramdisk_size=16777216 lvm2root=/dev/sda1 rw quiet
splash=silent
initrd /boot/initrd.img
}

then it works and loads the installer GUI.

I also note that it does not change to 1024x768 when booting via grub4dos,
so I added

vga=791

and now it works!!!







On 19 May 2017 at 12:46, Fabian Grünbichler 
wrote:

> On Fri, May 19, 2017 at 10:27:20AM +0100, Steve wrote:
> > If I type xinit it says /bin/sh: xinit: not found
> >
> > I am the author of easy2boot which is a USB multiboot tool to allow
> people
> > to boot from 100's of different ISOs (or images) all from one USB stick.
> > I have been asked by a user to get proxmox 4 working.
> > 3.2 works because I can run the unconfigured.sh from the command line
> >
> > http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-
> to-easy2boot.html
> > http://www.easy2boot.com
> >
> > I tried setting proxdebug and  root=/dev/sdb1  or lvm2root=/dev/sdb1 to
> get
> > it to mount the FAT32 partition to /mnt. I do not need to manually use
> any
> > mount commands, it just automatically runs init but this causes an early
> > error message of
> > mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
> > but if I use the mount command I can see that /mnt is present as a vfat
> > /dev/sdb1
> > If I press CTRL+D to continue, it fails in the exact same place with
> > Installation aborted - unable to continue.
> > Note that this is not using my script at all, just the original init
> script
> > - I have not broken into the boot process because it picks up the
> lvm2root
> > parameter.
> >
> > I am so *near*, yet I just cannot get the unconfigured.sh script to run
> in
> > this way...
> >
> > thanks for your help.
> > Steve
>
> I just did a quick test run using Grub:
>
> loopback test PATHTOISO
> linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw
> initrd (test)/boot/initrd.img
> boot
>
> drops me into the initrd debug shell
>
> if I do the following (major/minor depend on your disk configuration,
>   check /sys/class/block/XXX/dev where XXX is your usb partition where
>   the iso is)
>
> mknod /tmp/usbdev b MAJOR MINOR
> mkdir /tmp/usbmnt
> mount /tmp/usbdev /tmp/usbmnt
> mount /tmp/usbmnt/PATHTOISO /mnt
>
> followed by lines 294ff of the init script launch the graphical
> installer (although the resolution is messed up - probably because I did
> not bother to change any of the graphic stuff in Grub), and I am able to
> complete the installation..
>
> so I think it must be something in your environment / setup.
>
> (note that there are TWO debug shells, one in the initrd with very
> limited commands, and one in the installer environment with access to a
> lot more tools - a quick test is to run something like "lsblk", since
> that only exists in the latter environment ;). maybe your switch to the
> installer environment did not work, and you are still in the initrd
> shell? that would explain why you can't execute "xinit")
>
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

[PVE-User] Any way to patch / force proxmox to support /etc/network/interfaces.d/*?

[Eugen Mayer]

Hallo,

due to the nature of deploying with chef and configuring my network, 
interfaces, bridges there, entries in /etc/network/interfaces.d/eth0 .. 
/etc/network/interfaces.d/vmbr0 are created.
The issue no is, that /etc/network/interfaces basically just includes 

source /etc/network/interfaces.d/*

and is empty. Proxmox does not support that, does not list me any interfaces in 
the UI and does not let me assign my KVM VM to any interface. Any way i could 
patch that / force that / give proxmox a static list of interfaces ?

Thanks

-- 
Eugen
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Steve]

See the blog post (end of page)
http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to-easy2boot.html

On 19 May 2017 at 12:51, Steve  wrote:

> I just found  a way to get it to work by modifying the grub menu and add
> lvm2root=/dev/sdX4
>
> where sdX4 is a partition on the USB drive which points directly to the
> ISO file.
> So I am booting from the ISO (mapped to the BIOS device (0xff) in
> grub4dos) which boots to the grub2 menu and then I add the lvm2root
> parameter.
>
> The strange thing is that if I boot from a FAT32 flat-file system and have
> the ISO mapped to a partition in exactly the same way, the init script
> fails.
>
>
>
> On 19 May 2017 at 12:46, Fabian Grünbichler 
> wrote:
>
>> On Fri, May 19, 2017 at 10:27:20AM +0100, Steve wrote:
>> > If I type xinit it says /bin/sh: xinit: not found
>> >
>> > I am the author of easy2boot which is a USB multiboot tool to allow
>> people
>> > to boot from 100's of different ISOs (or images) all from one USB stick.
>> > I have been asked by a user to get proxmox 4 working.
>> > 3.2 works because I can run the unconfigured.sh from the command line
>> >
>> > http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to-
>> easy2boot.html
>> > http://www.easy2boot.com
>> >
>> > I tried setting proxdebug and  root=/dev/sdb1  or lvm2root=/dev/sdb1 to
>> get
>> > it to mount the FAT32 partition to /mnt. I do not need to manually use
>> any
>> > mount commands, it just automatically runs init but this causes an early
>> > error message of
>> > mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
>> > but if I use the mount command I can see that /mnt is present as a vfat
>> > /dev/sdb1
>> > If I press CTRL+D to continue, it fails in the exact same place with
>> > Installation aborted - unable to continue.
>> > Note that this is not using my script at all, just the original init
>> script
>> > - I have not broken into the boot process because it picks up the
>> lvm2root
>> > parameter.
>> >
>> > I am so *near*, yet I just cannot get the unconfigured.sh script to run
>> in
>> > this way...
>> >
>> > thanks for your help.
>> > Steve
>>
>> I just did a quick test run using Grub:
>>
>> loopback test PATHTOISO
>> linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw
>> initrd (test)/boot/initrd.img
>> boot
>>
>> drops me into the initrd debug shell
>>
>> if I do the following (major/minor depend on your disk configuration,
>>   check /sys/class/block/XXX/dev where XXX is your usb partition where
>>   the iso is)
>>
>> mknod /tmp/usbdev b MAJOR MINOR
>> mkdir /tmp/usbmnt
>> mount /tmp/usbdev /tmp/usbmnt
>> mount /tmp/usbmnt/PATHTOISO /mnt
>>
>> followed by lines 294ff of the init script launch the graphical
>> installer (although the resolution is messed up - probably because I did
>> not bother to change any of the graphic stuff in Grub), and I am able to
>> complete the installation..
>>
>> so I think it must be something in your environment / setup.
>>
>> (note that there are TWO debug shells, one in the initrd with very
>> limited commands, and one in the installer environment with access to a
>> lot more tools - a quick test is to run something like "lsblk", since
>> that only exists in the latter environment ;). maybe your switch to the
>> installer environment did not work, and you are still in the initrd
>> shell? that would explain why you can't execute "xinit")
>>
>> ___
>> pve-user mailing list
>> pve-user@pve.proxmox.com
>> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>
>
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Steve]

I just found  a way to get it to work by modifying the grub menu and add
lvm2root=/dev/sdX4

where sdX4 is a partition on the USB drive which points directly to the ISO
file.
So I am booting from the ISO (mapped to the BIOS device (0xff) in grub4dos)
which boots to the grub2 menu and then I add the lvm2root parameter.

The strange thing is that if I boot from a FAT32 flat-file system and have
the ISO mapped to a partition in exactly the same way, the init script
fails.



On 19 May 2017 at 12:46, Fabian Grünbichler 
wrote:

> On Fri, May 19, 2017 at 10:27:20AM +0100, Steve wrote:
> > If I type xinit it says /bin/sh: xinit: not found
> >
> > I am the author of easy2boot which is a USB multiboot tool to allow
> people
> > to boot from 100's of different ISOs (or images) all from one USB stick.
> > I have been asked by a user to get proxmox 4 working.
> > 3.2 works because I can run the unconfigured.sh from the command line
> >
> > http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-
> to-easy2boot.html
> > http://www.easy2boot.com
> >
> > I tried setting proxdebug and  root=/dev/sdb1  or lvm2root=/dev/sdb1 to
> get
> > it to mount the FAT32 partition to /mnt. I do not need to manually use
> any
> > mount commands, it just automatically runs init but this causes an early
> > error message of
> > mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
> > but if I use the mount command I can see that /mnt is present as a vfat
> > /dev/sdb1
> > If I press CTRL+D to continue, it fails in the exact same place with
> > Installation aborted - unable to continue.
> > Note that this is not using my script at all, just the original init
> script
> > - I have not broken into the boot process because it picks up the
> lvm2root
> > parameter.
> >
> > I am so *near*, yet I just cannot get the unconfigured.sh script to run
> in
> > this way...
> >
> > thanks for your help.
> > Steve
>
> I just did a quick test run using Grub:
>
> loopback test PATHTOISO
> linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw
> initrd (test)/boot/initrd.img
> boot
>
> drops me into the initrd debug shell
>
> if I do the following (major/minor depend on your disk configuration,
>   check /sys/class/block/XXX/dev where XXX is your usb partition where
>   the iso is)
>
> mknod /tmp/usbdev b MAJOR MINOR
> mkdir /tmp/usbmnt
> mount /tmp/usbdev /tmp/usbmnt
> mount /tmp/usbmnt/PATHTOISO /mnt
>
> followed by lines 294ff of the init script launch the graphical
> installer (although the resolution is messed up - probably because I did
> not bother to change any of the graphic stuff in Grub), and I am able to
> complete the installation..
>
> so I think it must be something in your environment / setup.
>
> (note that there are TWO debug shells, one in the initrd with very
> limited commands, and one in the installer environment with access to a
> lot more tools - a quick test is to run something like "lsblk", since
> that only exists in the latter environment ;). maybe your switch to the
> installer environment did not work, and you are still in the initrd
> shell? that would explain why you can't execute "xinit")
>
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Fabian Grünbichler]

On Fri, May 19, 2017 at 10:27:20AM +0100, Steve wrote:
> If I type xinit it says /bin/sh: xinit: not found
> 
> I am the author of easy2boot which is a USB multiboot tool to allow people
> to boot from 100's of different ISOs (or images) all from one USB stick.
> I have been asked by a user to get proxmox 4 working.
> 3.2 works because I can run the unconfigured.sh from the command line
> 
> http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to-easy2boot.html
> http://www.easy2boot.com
> 
> I tried setting proxdebug and  root=/dev/sdb1  or lvm2root=/dev/sdb1 to get
> it to mount the FAT32 partition to /mnt. I do not need to manually use any
> mount commands, it just automatically runs init but this causes an early
> error message of
> mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
> but if I use the mount command I can see that /mnt is present as a vfat
> /dev/sdb1
> If I press CTRL+D to continue, it fails in the exact same place with
> Installation aborted - unable to continue.
> Note that this is not using my script at all, just the original init script
> - I have not broken into the boot process because it picks up the lvm2root
> parameter.
> 
> I am so *near*, yet I just cannot get the unconfigured.sh script to run in
> this way...
> 
> thanks for your help.
> Steve

I just did a quick test run using Grub:

loopback test PATHTOISO
linux (test)/boot/linux26 proxdebug ramdisk_size=16777216 rw
initrd (test)/boot/initrd.img
boot

drops me into the initrd debug shell

if I do the following (major/minor depend on your disk configuration,
  check /sys/class/block/XXX/dev where XXX is your usb partition where
  the iso is)

mknod /tmp/usbdev b MAJOR MINOR
mkdir /tmp/usbmnt
mount /tmp/usbdev /tmp/usbmnt
mount /tmp/usbmnt/PATHTOISO /mnt

followed by lines 294ff of the init script launch the graphical
installer (although the resolution is messed up - probably because I did
not bother to change any of the graphic stuff in Grub), and I am able to
complete the installation..

so I think it must be something in your environment / setup.

(note that there are TWO debug shells, one in the initrd with very
limited commands, and one in the installer environment with access to a
lot more tools - a quick test is to run something like "lsblk", since
that only exists in the latter environment ;). maybe your switch to the
installer environment did not work, and you are still in the initrd
shell? that would explain why you can't execute "xinit")

___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Problems with backup process and NFS

[Fabian Grünbichler]

On Fri, May 19, 2017 at 12:49:21PM +0200, Uwe Sauter wrote:
> Am 19.05.2017 um 11:53 schrieb Fabian Grünbichler:
> > On Fri, May 19, 2017 at 11:26:35AM +0200, Uwe Sauter wrote:
> >> Hi Fabian,
> >>
> >> thanks for looking into this.
> >>
> >> As I already mentioned yesterday my NFS setup tries to use TCP as much as 
> >> possible so the only UDP port used / allowed in the NFS
> >> servers firewall is udp/111 for Portmapper (to allow showmount to work).
> >>
>  Issue 1:
>  Backups failed tonight with "Error: mount error: mount.nfs: 
>  /mnt/pve/aurel is busy or already mounted".
> 
>  Question 1:
>  Do NFS shares that should be used for backups need to be "disabled" so 
>  that the backup process just mount the share in preparation
>  of the backup? If so, there is a problem with the WebUI as I cannot 
>  select a disabled storage location when defining or editing a
>  backup job.
> 
> >>>
> >>> no. I think your NFS share is (wrongly) detected as unmounted, since
> >>> activate_storage in the NFS plugin will try to mount if nfs_is_mounted
> >>> returned undef. in general activate_storage is supposed to detect if the
> >>> storage is already activated and turn into a no-op if needed, and
> >>> calling storage can treat it as idempotent.
> >>>
> >>> what does "grep aurel /proc/mounts" say on this machine?
> >>
> >> # grep aurel /proc/mounts
> >> :/backup/proxmox-infra /mnt/pve/aurel nfs
> >> rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr= >>  of
> >> server>,mountvers=3,mountport=892,mountproto=tcp,local_lock=none,addr=141.58.1.15
> >>  0 0
> > 
> > that looks okay..
> > 
> >>
> >>>
> 
>  Issue 2:
>  When the backup process failed no email was sent to the specified 
>  address though email notification mode is set to "always".
>  Emails in general do work, at least apticron sends update notifications 
>  and sending mails from CLI also works.
> 
>  Question 2a:
>  Why was no email sent after the backup process failed?
> 
> >>>
> >>> can you post the complete log?
> >>
> >> Where can I find that?
> > 
> > check the node's task history - should have an entry for the backup job
> > including log.
> 
> Opening the task gives:
> 
> OUTPUT: TASK ERROR: mount error: mount.nfs: /mnt/pve/aurel is busy or already 
> mounted
> 
> STATUS: stopped: mount error: mount.nfs: /mnt/pve/aurel is busy or already 
> mounted
> 
> 
> Opening the log file in /var/log/pve/tasks for that tasks gives the same as 
> above OUTPUT.
> 
> 
> 
> > 
> >>
> >>>
>  Question 2b:
>  Does the WebUI use a different method for sending emails? If so where 
>  can this be configured?
> >>>
> >>> different from what?
> >>>
> >>
> >> Different from what apticron and "echo test | mail -s test  >> address>" use.
> >>
> > 
> > there is /root/.forward which points to pvemailforward which uses
> > "sendmail -bm -N never -f  " (using 'root' or the value from
> > datacenter.cfg as sender, and the adress of 'root@pam' as recipient),
> > and PVE::Tools::sendmail() (which is used by vzdump) which uses
> > "sendmail -B 8BITMIME -f  " (with configurable sender and
> > recipient). vzdump sets the sender to the one from datacenter.cfg as
> > well, and the recipient to what is configured for the backup job.
> > 
> 
> # cat /etc/pve/datacenter.cfg
> keyboard: de
> 
> # cat /etc/pve/user.cfg
> user:root@pam:1:0:
> 
> I suspect that something just doesn't send emails in that specific error case…

yes, seems like activate_storage is called very early on to retrieve
maxfiles and dumpdir via PVE::API2::VZDump (POST) -> PVE::VZDump->new()
-> PVE::VZDump::storage_info() , and that call is not guarded by an
eval, thus no error handling and sendmail is triggered. can you file a
bug for that? thanks!

the underlying issue is still unclear to me.. can you post the output of
the following snippet (insert your correct IP)

perl -e '
use strict;
use warnings;
use PVE::Storage::NFSPlugin;
my $server = "INSERTNFSSERVERIPHERE";
my $export = "/backup/proxmox-infra";
my $mountpoint = "/mnt/pve/aurel";
print PVE::Storage::NFSPlugin::nfs_is_mounted($server, $export, $mountpoint, 
undef), "\n";
'

if that does not output anything, the following might also be
interesting (feel free to censor as you see fit):

perl -e 'use strict; use warnings; use PVE::ProcFSTools; use Data::Dumper; 
print Dumper(PVE::ProcFSTools::parse_proc_mounts());'

> 
> Is there a way to test the mail configuration using PVE's mechanism?

yes, just pipe your mail into the the sendmail command I posted ;) to
check past mails, you can also use something like

journalctl -b | grep 'pvemail\|postfix'

___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Problems with backup process and NFS

[Uwe Sauter]

Am 19.05.2017 um 11:53 schrieb Fabian Grünbichler:
> On Fri, May 19, 2017 at 11:26:35AM +0200, Uwe Sauter wrote:
>> Hi Fabian,
>>
>> thanks for looking into this.
>>
>> As I already mentioned yesterday my NFS setup tries to use TCP as much as 
>> possible so the only UDP port used / allowed in the NFS
>> servers firewall is udp/111 for Portmapper (to allow showmount to work).
>>
 Issue 1:
 Backups failed tonight with "Error: mount error: mount.nfs: /mnt/pve/aurel 
 is busy or already mounted".

 Question 1:
 Do NFS shares that should be used for backups need to be "disabled" so 
 that the backup process just mount the share in preparation
 of the backup? If so, there is a problem with the WebUI as I cannot select 
 a disabled storage location when defining or editing a
 backup job.

>>>
>>> no. I think your NFS share is (wrongly) detected as unmounted, since
>>> activate_storage in the NFS plugin will try to mount if nfs_is_mounted
>>> returned undef. in general activate_storage is supposed to detect if the
>>> storage is already activated and turn into a no-op if needed, and
>>> calling storage can treat it as idempotent.
>>>
>>> what does "grep aurel /proc/mounts" say on this machine?
>>
>> # grep aurel /proc/mounts
>> :/backup/proxmox-infra /mnt/pve/aurel nfs
>> rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=>  of
>> server>,mountvers=3,mountport=892,mountproto=tcp,local_lock=none,addr=141.58.1.15
>>  0 0
> 
> that looks okay..
> 
>>
>>>

 Issue 2:
 When the backup process failed no email was sent to the specified address 
 though email notification mode is set to "always".
 Emails in general do work, at least apticron sends update notifications 
 and sending mails from CLI also works.

 Question 2a:
 Why was no email sent after the backup process failed?

>>>
>>> can you post the complete log?
>>
>> Where can I find that?
> 
> check the node's task history - should have an entry for the backup job
> including log.

Opening the task gives:

OUTPUT: TASK ERROR: mount error: mount.nfs: /mnt/pve/aurel is busy or already 
mounted

STATUS: stopped: mount error: mount.nfs: /mnt/pve/aurel is busy or already 
mounted


Opening the log file in /var/log/pve/tasks for that tasks gives the same as 
above OUTPUT.



> 
>>
>>>
 Question 2b:
 Does the WebUI use a different method for sending emails? If so where can 
 this be configured?
>>>
>>> different from what?
>>>
>>
>> Different from what apticron and "echo test | mail -s test > address>" use.
>>
> 
> there is /root/.forward which points to pvemailforward which uses
> "sendmail -bm -N never -f  " (using 'root' or the value from
> datacenter.cfg as sender, and the adress of 'root@pam' as recipient),
> and PVE::Tools::sendmail() (which is used by vzdump) which uses
> "sendmail -B 8BITMIME -f  " (with configurable sender and
> recipient). vzdump sets the sender to the one from datacenter.cfg as
> well, and the recipient to what is configured for the backup job.
> 

# cat /etc/pve/datacenter.cfg
keyboard: de

# cat /etc/pve/user.cfg
user:root@pam:1:0:

I suspect that something just doesn't send emails in that specific error case…

Is there a way to test the mail configuration using PVE's mechanism?


Regards,

Uwe


___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Problem running any VM with more then 1 Core ( PVE 4.x)

[Fabian Grünbichler]

> Eugen Mayer  hat am 19. Mai 2017 um 12:04 
> geschrieben:
> 
> 
> Hello,
> 
> having an issue with proxmox 4.x running any VM with more then 1 core.
> 
> Hardware:
>  - Intel(R) Xeon(R) CPU E3-1275 v5 @ 3.60GHz
>  - 64GB ram
>  - HW raid SSD
> 
> PVE 4.x just got installed freshly, just 1 other VM on that box ( 1core 
> opnsense ) and nothing else, so fairly idle and nothing really to be worry 
> about.
> 
> I tried boot rancheros 1.0.1 and grml 2014.11 ( both 64bit ), both have the 
> same pattern, when i boot them first, it works, when i reboot them using the 
> cli
>  - grub shows up ( if present as menu )
>  - selecting anything leads to a stalled VM which i only can stop using qm 
> kill <>
> 
> Using 1 core only, everything works just fine 2-4 broke, did not try more. It 
> does not matter if i boot an iso or e.g an installed version of rancheros, 
> reboot stalls every single time.
> 
> I have never seen grml not boot up on anything yet, pretty sure that is a 
> general issue.
> 
> Logs / Details:
>  - dmsg just shows nothing during that happening
>  - pve-manager 4.4-13
>  - kernel: 4.9.0-0.bpo.2-amd64 #1 SMP Debian 4.9.18-1~bpo8+1
>  - debian 8.8 fully upgraded
>  - nothing runs on the host except shorewall
> 
> Can i provide anything else? Any clues?

you run a non-PVE kernel - which is a completely untested and unsupported 
configuration. please revert to the PVE 4.4 kernel and test again. if the issue 
persists, please include "pveversion -v" and "qm config VMID"

___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Steve]

If I type xinit it says /bin/sh: xinit: not found

I am the author of easy2boot which is a USB multiboot tool to allow people
to boot from 100's of different ISOs (or images) all from one USB stick.
I have been asked by a user to get proxmox 4 working.
3.2 works because I can run the unconfigured.sh from the command line

http://rmprepusb.blogspot.co.uk/2014/03/add-proxmox-isos-to-easy2boot.html
http://www.easy2boot.com

I tried setting proxdebug and  root=/dev/sdb1  or lvm2root=/dev/sdb1 to get
it to mount the FAT32 partition to /mnt. I do not need to manually use any
mount commands, it just automatically runs init but this causes an early
error message of
mount: mounting /dev/sdb1 on /mnt failed: Invalid argument
but if I use the mount command I can see that /mnt is present as a vfat
/dev/sdb1
If I press CTRL+D to continue, it fails in the exact same place with
Installation aborted - unable to continue.
Note that this is not using my script at all, just the original init script
- I have not broken into the boot process because it picks up the lvm2root
parameter.

I am so *near*, yet I just cannot get the unconfigured.sh script to run in
this way...

thanks for your help.
Steve

On 19 May 2017 at 10:04, Fabian Grünbichler 
wrote:

> On Fri, May 19, 2017 at 09:40:54AM +0100, Steve wrote:
> > I tried proxdebug. No extra messages are generated after the network has
> > initialised.
> > There is no log in /tmp folder ? Has the log moved?
> >
> > How do I run xinit? Where is it?
> > Do you mean init? If I run this it says must be run as PID 1 - how can I
> > fix this (sorry, I am not a linux guru!)
> >
>
> just type "xinit" in the debug shell. but if you are not comfortable
> with this kind of debugging, you might be better off just (temporarily)
> "sacrificing" a thumb drive for the PVE installer instead of trying to
> get this non-standard way to boot it to work ;)
>
> I hope to fix the initrd during the 5.x release cycleto to allow booting
> in some kind of loopback mode, but it's a low priority item on my todo
> list..
>
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Problems with backup process and NFS

[Uwe Sauter]

Hi Fabian,

thanks for looking into this.

As I already mentioned yesterday my NFS setup tries to use TCP as much as 
possible so the only UDP port used / allowed in the NFS
servers firewall is udp/111 for Portmapper (to allow showmount to work).

>> Issue 1:
>> Backups failed tonight with "Error: mount error: mount.nfs: /mnt/pve/aurel 
>> is busy or already mounted".
>>
>> Question 1:
>> Do NFS shares that should be used for backups need to be "disabled" so that 
>> the backup process just mount the share in preparation
>> of the backup? If so, there is a problem with the WebUI as I cannot select a 
>> disabled storage location when defining or editing a
>> backup job.
>>
> 
> no. I think your NFS share is (wrongly) detected as unmounted, since
> activate_storage in the NFS plugin will try to mount if nfs_is_mounted
> returned undef. in general activate_storage is supposed to detect if the
> storage is already activated and turn into a no-op if needed, and
> calling storage can treat it as idempotent.
> 
> what does "grep aurel /proc/mounts" say on this machine?

# grep aurel /proc/mounts
:/backup/proxmox-infra /mnt/pve/aurel nfs
rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=,mountvers=3,mountport=892,mountproto=tcp,local_lock=none,addr=141.58.1.15
 0 0

> 
>>
>> Issue 2:
>> When the backup process failed no email was sent to the specified address 
>> though email notification mode is set to "always".
>> Emails in general do work, at least apticron sends update notifications and 
>> sending mails from CLI also works.
>>
>> Question 2a:
>> Why was no email sent after the backup process failed?
>>
> 
> can you post the complete log?

Where can I find that?

> 
>> Question 2b:
>> Does the WebUI use a different method for sending emails? If so where can 
>> this be configured?
> 
> different from what?
> 

Different from what apticron and "echo test | mail -s test " 
use.

Regards,

Uwe
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Problems with backup process and NFS

[Fabian Grünbichler]

On Fri, May 19, 2017 at 10:43:26AM +0200, Uwe Sauter wrote:
> Hi all,
> 
> after having succeeded to have an almost TCP-based NFS share mounted (see 
> yesterday's thread) I'm now struggling with the backup
> process itself.
> 
> Definition of NFS share in /etc/pve/storage.cfg is:
> 
> nfs: aurel
>   export /backup/proxmox-infra
>   path /mnt/pve/aurel
>   server 
>   content backup
>   maxfiles 30
>   options vers=3
> 
> 
> With this definition, :/backup/proxmox-infra is always mounted on 
> /mnt/pve/aurel on every one of my PVE servers.
> 
> 
> Definition of backup job is:
>   Nodes: all
>   Storage: aurel
>   Day of week: Mon-Sun
>   Start time: 22:00
>   Selection mode: Include selected VMs
>   Send email to: 
>   Email notification: always
>   compression: lzo
>   Mode: Snapshot
>   Enable: true
>   VMs: 
> 
> 
> 
> Issue 1:
> Backups failed tonight with "Error: mount error: mount.nfs: /mnt/pve/aurel is 
> busy or already mounted".
> 
> Question 1:
> Do NFS shares that should be used for backups need to be "disabled" so that 
> the backup process just mount the share in preparation
> of the backup? If so, there is a problem with the WebUI as I cannot select a 
> disabled storage location when defining or editing a
> backup job.
> 

no. I think your NFS share is (wrongly) detected as unmounted, since
activate_storage in the NFS plugin will try to mount if nfs_is_mounted
returned undef. in general activate_storage is supposed to detect if the
storage is already activated and turn into a no-op if needed, and
calling storage can treat it as idempotent.

what does "grep aurel /proc/mounts" say on this machine?

> 
> Issue 2:
> When the backup process failed no email was sent to the specified address 
> though email notification mode is set to "always".
> Emails in general do work, at least apticron sends update notifications and 
> sending mails from CLI also works.
> 
> Question 2a:
> Why was no email sent after the backup process failed?
> 

can you post the complete log?

> Question 2b:
> Does the WebUI use a different method for sending emails? If so where can 
> this be configured?

different from what?

___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Fabian Grünbichler]

On Fri, May 19, 2017 at 09:40:54AM +0100, Steve wrote:
> I tried proxdebug. No extra messages are generated after the network has
> initialised.
> There is no log in /tmp folder ? Has the log moved?
> 
> How do I run xinit? Where is it?
> Do you mean init? If I run this it says must be run as PID 1 - how can I
> fix this (sorry, I am not a linux guru!)
> 

just type "xinit" in the debug shell. but if you are not comfortable
with this kind of debugging, you might be better off just (temporarily)
"sacrificing" a thumb drive for the PVE installer instead of trying to
get this non-standard way to boot it to work ;)

I hope to fix the initrd during the 5.x release cycleto to allow booting
in some kind of loopback mode, but it's a low priority item on my todo
list..

___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

[PVE-User] Problems with backup process and NFS

[Uwe Sauter]

Hi all,

after having succeeded to have an almost TCP-based NFS share mounted (see 
yesterday's thread) I'm now struggling with the backup
process itself.

Definition of NFS share in /etc/pve/storage.cfg is:

nfs: aurel
export /backup/proxmox-infra
path /mnt/pve/aurel
server 
content backup
maxfiles 30
options vers=3


With this definition, :/backup/proxmox-infra is always mounted on 
/mnt/pve/aurel on every one of my PVE servers.


Definition of backup job is:
  Nodes: all
  Storage: aurel
  Day of week: Mon-Sun
  Start time: 22:00
  Selection mode: Include selected VMs
  Send email to: 
  Email notification: always
  compression: lzo
  Mode: Snapshot
  Enable: true
  VMs: 



Issue 1:
Backups failed tonight with "Error: mount error: mount.nfs: /mnt/pve/aurel is 
busy or already mounted".

Question 1:
Do NFS shares that should be used for backups need to be "disabled" so that the 
backup process just mount the share in preparation
of the backup? If so, there is a problem with the WebUI as I cannot select a 
disabled storage location when defining or editing a
backup job.


Issue 2:
When the backup process failed no email was sent to the specified address 
though email notification mode is set to "always".
Emails in general do work, at least apticron sends update notifications and 
sending mails from CLI also works.

Question 2a:
Why was no email sent after the backup process failed?

Question 2b:
Does the WebUI use a different method for sending emails? If so where can this 
be configured?

Regards,

Uwe
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Steve]

I tried proxdebug. No extra messages are generated after the network has
initialised.
There is no log in /tmp folder ? Has the log moved?

How do I run xinit? Where is it?
Do you mean init? If I run this it says must be run as PID 1 - how can I
fix this (sorry, I am not a linux guru!)



On 19 May 2017 at 09:12, Fabian Grünbichler 
wrote:

> On Fri, May 19, 2017 at 08:28:17AM +0100, Steve wrote:
> > Thanks
> > I tried that.
> > I made a new .sh from the portion of the initrd that mounts all the
> > squashfs files and runs unconfigured.sh.
> > It seems to almost work, but it gets to Detecting network settings...
> done
> > and then says
> > \nInstallation aborted - unable to continue
> >
> > any ideas why?
> >
>
> boot it with "proxdebug" as part of the kernel cmdline and examine the
> logs. you can also manually run "xinit" in the debug shell to restart
> the installer from the debug shell.
>
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Fabian Grünbichler]

On Fri, May 19, 2017 at 08:28:17AM +0100, Steve wrote:
> Thanks
> I tried that.
> I made a new .sh from the portion of the initrd that mounts all the
> squashfs files and runs unconfigured.sh.
> It seems to almost work, but it gets to Detecting network settings... done
> and then says
> \nInstallation aborted - unable to continue
> 
> any ideas why?
> 

boot it with "proxdebug" as part of the kernel cmdline and examine the
logs. you can also manually run "xinit" in the debug shell to restart
the installer from the debug shell.

___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Steve]

P.S.
As an experiment, I even inserted a dd'd flash drive containing the proxmox
ISO (which works if I boot to it) and then booted from my multiboot USB
drive to the shell and then mounted /mnt as the flash drive
mount /dev/sdc /mnt

then I ran the modified script.
I gave the same fail message.
So that seems to indicate that something is wrong with the script or
environment when I run the script?

The script I run starts with
if [ -f /mnt/pve-installer.squashfs ]; then
echo this is a Proxmox VE installation CD

if ! mount -t squashfs -o ro,loop /mnt/pve-base.squashfs
/mnt/.pve-base; then
debugsh_err_reboot "mount pve-base.squashfs failed"
fi

any ideas what is not set up before this?

Steve






On 19 May 2017 at 07:34, Fabian Grünbichler 
wrote:

> On Thu, May 18, 2017 at 07:08:36PM +0100, Steve wrote:
> > Thanks for the quick reply.
> > I am booting from the ISO file itself which is on a multiboot USB drive.
> > In previous versions, you could boot to the shell, mount the ISO as /mnt
> > and then start the install by running unconfigured.sh.
> >
> > So basically, if I boot to the shell, how can I start the install from
> the
> > contents of the CD/ISO.
> >
>
> you need to mount the contained squashfs files in the right order on the
> right places, make an overlayfs and then bind mount the iso into that.
> then you can chroot and run the unconfigured.sh script. basically do all
> the steps that the initrd contained on the iso does ;)
>
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Steve]

Thanks
I tried that.
I made a new .sh from the portion of the initrd that mounts all the
squashfs files and runs unconfigured.sh.
It seems to almost work, but it gets to Detecting network settings... done
and then says
\nInstallation aborted - unable to continue

any ideas why?




On 19 May 2017 at 07:34, Fabian Grünbichler 
wrote:

> On Thu, May 18, 2017 at 07:08:36PM +0100, Steve wrote:
> > Thanks for the quick reply.
> > I am booting from the ISO file itself which is on a multiboot USB drive.
> > In previous versions, you could boot to the shell, mount the ISO as /mnt
> > and then start the install by running unconfigured.sh.
> >
> > So basically, if I boot to the shell, how can I start the install from
> the
> > contents of the CD/ISO.
> >
>
> you need to mount the contained squashfs files in the right order on the
> right places, make an overlayfs and then bind mount the iso into that.
> then you can chroot and run the unconfigured.sh script. basically do all
> the steps that the initrd contained on the iso does ;)
>
> ___
> pve-user mailing list
> pve-user@pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] sbin/unconfigured.sh

[Fabian Grünbichler]

On Thu, May 18, 2017 at 07:08:36PM +0100, Steve wrote:
> Thanks for the quick reply.
> I am booting from the ISO file itself which is on a multiboot USB drive.
> In previous versions, you could boot to the shell, mount the ISO as /mnt
> and then start the install by running unconfigured.sh.
> 
> So basically, if I boot to the shell, how can I start the install from the
> contents of the CD/ISO.
> 

you need to mount the contained squashfs files in the right order on the
right places, make an overlayfs and then bind mount the iso into that.
then you can chroot and run the unconfigured.sh script. basically do all
the steps that the initrd contained on the iso does ;)

___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user