so my original issue was started by installing postfix from wrong repository .
using joynet on another system caused no issues. On Sun, May 22, 2016 at 6:52 AM, Günther Alka <a...@hfg-gmuend.de> wrote: > I would suggest the following procedure on problems after system > modifications > > Get a list of all available bootenvironments (BE) either from napp-it menu > snapshots >> bootenvironment or with a beadm list. This also shows the > current BE and the active one that is the default on next bootup. > > Prior critical actions, you can create a BE manually what allows a "go > back to the state prior this action" > > From your list there is a quite new BE (pre_napp-it-16.03f) what is the > system state prior last napp-it update. You can select this BE during > bootup from a list. If it works, redo the napp-it update, activate this BE > in menu snapshot >> bootenvironment and delete the not working BE there. > > Prior this, you may run the napp-it backup job that saves all current > napp-it settings to your data pool so you can restore them to the former > bootenvironment ex via menu User > Restore settings > > Gea > > > > > > On 20.05.2016 03:48, Robert Fantini wrote: > > after the rollback, per was the same version , and napp-it had same issue. > > Here are our zfs filesystems: > > # alias df > alias df='zfs list -t filesystem' > sys4 ~ # df > NAME USED AVAIL REFER MOUNTPOINT > data 175G 1.68T 27.2K /data > data/backup_napp-it 265M 1.51T 37.8M > /data/backup_napp-it > rpool 23.9G 437G 24.5K /rpool > rpool/ROOT 5.82G 437G 19K legacy > rpool/ROOT/omnios 273M 437G 2.97G / > rpool/ROOT/omnios-1 5.55G 437G 3.18G / > rpool/ROOT/omnios-1-backup-1 41K 437G 3.34G / > rpool/ROOT/omnios-backup-1 63K 437G 1.64G / > rpool/ROOT/omniosvar 19K 437G 19K legacy > rpool/ROOT/pre_download_16.03f_1463010047 1K 437G 2.92G / > rpool/ROOT/pre_napp-it-16.02f 35K 437G 1.63G / > rpool/ROOT/pre_napp-it-16.03f 41K 437G 3.19G / > rpool/export 38K 437G 19K /export > rpool/export/home 19K 437G 19K > /export/home > > I had done this to roll back: > zfs rollback -r rpool/ROOT/omnios@2016-05-19-150000 > > In case you know omnios/napp-it , is there another file system which > should be rolled back to fix the napp-it storage? > > > On Thu, May 19, 2016 at 6:46 PM, Robert Fantini <robertfant...@gmail.com> > wrote: > >> so I was installing postfix to use with a log check script. instead will >> do remote logging ... >> >> to fix our issue I think doing a zfs rollback . following >> http://omnios.omniti.com/wiki.php/GeneralAdministration ... >> >> we've hourly snapshots. >> >> so I plan to do this: >> >> 1- shut down all virtual machines [ kvm on iscsi . using proxmox. ] >> 2- init 1 >> 3- zfs rollback rpool/ROOT/omnios@2016-05-19-150000 >> 4- reboot >> >> Or am I being overly cautions? >> >> >> >> On Thu, May 19, 2016 at 5:32 PM, Robert Fantini < >> <robertfant...@gmail.com>robertfant...@gmail.com> wrote: >> >>> so I assume that when postfix got installed, an update to perl occurred. >>> >>> can someone please point me in the direction to install the prior perl >>> version? >>> >>> PS: others have had a similar issue: >>> >>> https://hardforum.com/threads/opensolaris-derived-zfs-nas-san-omnios-openindiana-solaris-and-napp-it.1573272/page-180#post-1041974303 >>> >>> On Thu, May 19, 2016 at 5:05 PM, Robert Fantini <robertfant...@gmail.com >>> > wrote: >>> >>>> >>>> ---------- Forwarded message ---------- >>>> From: Robert Fantini < <robertfant...@gmail.com>robertfant...@gmail.com >>>> > >>>> Date: Thu, May 19, 2016 at 4:43 PM >>>> Subject: Re: [OmniOS-discuss] after installing postfix, got 'wrong ELF >>>> class' issue >>>> To: Dan McDonald < <dan...@omniti.com>dan...@omniti.com> >>>> >>>> >>>> # /usr/perl5/5.16.1/bin/i386/perl >>>> /var/web-gui/data/napp-it/zfsos/_lib/scripts/auto.pl >>>> Perl API version v5.14.0 of IO::Tty does not match v5.16.0 at >>>> /usr/perl5/5.16.1/lib/i86pc-solaris-thread-multi-64int/DynaLoader.pm line >>>> 213. >>>> Compilation failed in require at >>>> /var/web-gui/data/napp-it/CGI/IO/Pty.pm line 7. >>>> BEGIN failed--compilation aborted at >>>> /var/web-gui/data/napp-it/CGI/IO/Pty.pm line 7. >>>> Compilation failed in require at >>>> /var/web-gui/data/napp-it/CGI/Expect.pm line 22. >>>> BEGIN failed--compilation aborted at >>>> /var/web-gui/data/napp-it/CGI/Expect.pm line 22. >>>> Compilation failed in require at >>>> /var/web-gui/data/napp-it/zfsos/_lib/illumos/zfslib.pl line 2816. >>>> BEGIN failed--compilation aborted at >>>> /var/web-gui/data/napp-it/zfsos/_lib/illumos/zfslib.pl line 2816. >>>> Compilation failed in require at >>>> /var/web-gui/data/napp-it/zfsos/_lib/scripts/auto.pl line 52. >>>> >>>> >>>> On Thu, May 19, 2016 at 4:40 PM, Dan McDonald < <dan...@omniti.com> >>>> dan...@omniti.com> wrote: >>>> >>>>> >>>>> > On May 19, 2016, at 4:32 PM, Robert Fantini < >>>>> <robertfant...@gmail.com>robertfant...@gmail.com> wrote: >>>>> > >>>>> > # /usr/bin/i386/perl /var/web-gui/data/napp-it/zfsos/_lib/scripts/ >>>>> auto.pl >>>>> > -bash: /usr/bin/i386/perl: No such file or directory >>>>> >>>>> Interesting. >>>>> >>>>> /usr/perl5/5.16.1/bin/i386/perl >>>>> >>>>> should work, but I wonder if our perl packaging should be a bit more >>>>> intelligent with symlinks in /usr/bin/{i386,amd64} as well? >>>>> >>>>> Dan >>>>> >>>>> >>>> >>>> >>> >> > > > _______________________________________________ > OmniOS-discuss mailing > listOmniOS-discuss@lists.omniti.comhttp://lists.omniti.com/mailman/listinfo/omnios-discuss > > > > > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss > >
_______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss