From serge.fonville at gmail.com Sun Dec 3 18:05:03 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Sun, 3 Dec 2017 19:05:03 +0100 Subject: [OmniOS-discuss] Keepalived in an LX branded zone Message-ID: Hi, I am currently trying to setup keepalived in an LX branded zone. Since I get a lot of errors that might be related to the fact it is an LX branded zone, I was wondering if someone would be so kind to shed their light on it. Especially since I never setup keepalived before, I am unsure if these errors are caused by the fact it is an LX branded zone, of just misconfiguration of keepalived. # Inside the zone keepalived.conf > global_defs { router_id haproxy01 > vrrp_version 3 > } > > vrrp_script check_haproxy { > script "/etc/keepalived/check_haproxy.sh" > interval 0.05 > fall 2 > rise 2 > } > > vrrp_instance haproxy_instance { > state MASTER > interface haproxy01vnic0 > virtual_router_id 25 > priority 150 > advert_int 0.05 > virtual_ipaddress { > 192.168.1.25/2 label haproxy01vnic0:0 > } > track_script { > check_haproxy > } > } > > keepalived -f /etc/keepalived/keepalived.conf -l -n > Starting Keepalived v1.3.5 (03/19,2017), git commit v1.3.5-6-g6fa32f2 > Unable to resolve default script username 'keepalived_script' - ignoring > Opening file '/etc/keepalived/keepalived.conf'. > Starting Healthcheck child process, pid=13481 > Initializing ipvs > Starting VRRP child process, pid=13482 > Registering Kernel netlink reflector > Registering Kernel netlink command channel > Error while registering gratuitous ARP shared channel > Opening file '/etc/keepalived/keepalived.conf'. > IPVS: Can't initialize ipvs: No such file or directory > Keepalived_vrrp exited due to segmentation fault (SIGSEGV). > Please report a bug at https://github.com/acassen/keepalived/issues > and include this log from when keepalived started, what happened > immediately before the crash, and your configuration file. > /etc/keepalived/check_haproxy.sh > #!/bin/bash > kill -0 $(cat /run/haproxy.pid) && echo 'OK' && exit 0 || echo 'NOK' && exit 1 > > # Inside the global zone cat /etc/zones/haproxy01.xml > > > "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1"> > brand="lx" ip-type="exclusive" debugid="20"> > > > > > > > > > > > > > uname -v omnios-r151022-f9693432c2 Any feedback or input is greatly appreciated! Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.fonville at gmail.com Tue Dec 5 09:06:55 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Tue, 5 Dec 2017 10:06:55 +0100 Subject: [OmniOS-discuss] Keepalived in an LX branded zone In-Reply-To: References: Message-ID: One of the possible alternatives would be to install zones with system/network/routing/vrrp, but then I still have the challenge that haproxy is not in https://pkg.omniosce.org/r151022/core/ Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-12-03 19:05 GMT+01:00 Serge Fonville : > Hi, > > I am currently trying to setup keepalived in an LX branded zone. > > Since I get a lot of errors that might be related to the fact it is an LX > branded zone, I was wondering if someone would be so kind to shed their > light on it. > > Especially since I never setup keepalived before, I am unsure if these > errors are caused by the fact it is an LX branded zone, of just > misconfiguration of keepalived. > > # Inside the zone > keepalived.conf > >> global_defs { router_id haproxy01 >> vrrp_version 3 >> } >> >> vrrp_script check_haproxy { >> script "/etc/keepalived/check_haproxy.sh" >> interval 0.05 >> fall 2 >> rise 2 >> } >> >> vrrp_instance haproxy_instance { >> state MASTER >> interface haproxy01vnic0 >> virtual_router_id 25 >> priority 150 >> advert_int 0.05 >> virtual_ipaddress { >> 192.168.1.25/2 label haproxy01vnic0:0 >> } >> track_script { >> check_haproxy >> } >> } >> >> > keepalived -f /etc/keepalived/keepalived.conf -l -n > >> Starting Keepalived v1.3.5 (03/19,2017), git commit v1.3.5-6-g6fa32f2 >> Unable to resolve default script username 'keepalived_script' - ignoring >> Opening file '/etc/keepalived/keepalived.conf'. >> Starting Healthcheck child process, pid=13481 >> Initializing ipvs >> Starting VRRP child process, pid=13482 >> Registering Kernel netlink reflector >> Registering Kernel netlink command channel >> Error while registering gratuitous ARP shared channel >> Opening file '/etc/keepalived/keepalived.conf'. >> IPVS: Can't initialize ipvs: No such file or directory >> Keepalived_vrrp exited due to segmentation fault (SIGSEGV). >> Please report a bug at https://github.com/acassen/keepalived/issues >> and include this log from when keepalived started, what happened >> immediately before the crash, and your configuration file. >> > > /etc/keepalived/check_haproxy.sh > >> #!/bin/bash >> kill -0 $(cat /run/haproxy.pid) && echo 'OK' && exit 0 || echo 'NOK' && exit 1 >> >> > # Inside the global zone > cat /etc/zones/haproxy01.xml > >> >> >> > "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1"> >> > autoboot="true" brand="lx" ip-type="exclusive" debugid="20"> >> >> >> >> >> >> >> >> >> >> >> >> >> > > uname -v > omnios-r151022-f9693432c2 > > Any feedback or input is greatly appreciated! > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > -------------- next part -------------- An HTML attachment was scrubbed... URL: From serge.fonville at gmail.com Wed Dec 6 15:28:48 2017 From: serge.fonville at gmail.com (Serge Fonville) Date: Wed, 6 Dec 2017 16:28:48 +0100 Subject: [OmniOS-discuss] Boot Environment not active after reboot Message-ID: Hi, I upgraded to r151024, but after the upgraded the new boot environment is not active. When I run beadmin activate, I get "Activation Successful", but after the reboot, it is not active. When I run reboot -f -e then it does activate and boot, but when I reboot normally, it is no longer active, even though it is marked R in beadm list. Any advice would be greatly appreciated. thanks in advance! Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl -------------- next part -------------- An HTML attachment was scrubbed... URL: From natxo.asenjo at gmail.com Sun Dec 10 20:24:23 2017 From: natxo.asenjo at gmail.com (Natxo Asenjo) Date: Sun, 10 Dec 2017 21:24:23 +0100 Subject: [OmniOS-discuss] [ot] recommendation on jbod enclosure (16-bay, preferably 24 bay) 2.5 inch sas/sata Message-ID: hi, the subject says it all, I guess. I am based in The Netherlands, but buying in the EU should be ok. I can only find very expensive Dell or HP kit (> EUR 5000) but I cannot seem to find in here something like this: https://www.neweggbusiness.com/product/product.aspx?item=9b-1uw-0036-00096 which looks a lot like what we are after Thanks in advance! -- Regards, Natxo -------------- next part -------------- An HTML attachment was scrubbed... URL: From mir at miras.org Sun Dec 10 23:48:14 2017 From: mir at miras.org (Michael Rasmussen) Date: Mon, 11 Dec 2017 00:48:14 +0100 Subject: [OmniOS-discuss] [ot] recommendation on jbod enclosure (16-bay, preferably 24 bay) 2.5 inch sas/sata In-Reply-To: References: Message-ID: <20171211004814.3e856c6b@sleipner.datanom.net> On Sun, 10 Dec 2017 21:24:23 +0100 Natxo Asenjo wrote: > hi, > > the subject says it all, I guess. > > I am based in The Netherlands, but buying in the EU should be ok. > > I can only find very expensive Dell or HP kit (> EUR 5000) but I cannot > seem to find in here something like this: > > https://www.neweggbusiness.com/product/product.aspx?item=9b-1uw-0036-00096 > > which looks a lot like what we are after > Something here? https://www.xcase.co.uk/collections/jbod-systems -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- /usr/games/fortune -es says: My mother drinks to forget she drinks. -- Crazy Jimmy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From matej at zunaj.si Mon Dec 11 17:29:29 2017 From: matej at zunaj.si (=?utf-8?Q?Matej_=C5=BDerovnik?=) Date: Mon, 11 Dec 2017 18:29:29 +0100 Subject: [OmniOS-discuss] [ot] recommendation on jbod enclosure (16-bay, preferably 24 bay) 2.5 inch sas/sata In-Reply-To: <20171211004814.3e856c6b@sleipner.datanom.net> References: <20171211004814.3e856c6b@sleipner.datanom.net> Message-ID: <62891C13-5F98-4B38-B538-0B90174B1F1D@zunaj.si> Maybe something like this: https://www.supermicro.com/products/chassis/3U/837/SC837E26-RJBOD1 I think the price is around 1500EUR. It?s only SAS2 though. I saw they have some newer 16-bay SAS3 JBODs. Matej > On 11 Dec 2017, at 00:48, Michael Rasmussen wrote: > > On Sun, 10 Dec 2017 21:24:23 +0100 > Natxo Asenjo wrote: > >> hi, >> >> the subject says it all, I guess. >> >> I am based in The Netherlands, but buying in the EU should be ok. >> >> I can only find very expensive Dell or HP kit (> EUR 5000) but I cannot >> seem to find in here something like this: >> >> https://www.neweggbusiness.com/product/product.aspx?item=9b-1uw-0036-00096 >> >> which looks a lot like what we are after >> > Something here? https://www.xcase.co.uk/collections/jbod-systems > > -- > Hilsen/Regards > Michael Rasmussen > > Get my public GnuPG keys: > michael rasmussen cc > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E > mir datanom net > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C > mir miras org > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 > -------------------------------------------------------------- > /usr/games/fortune -es says: > My mother drinks to forget she drinks. > -- Crazy Jimmy > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss at lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at omniti.com Fri Dec 15 23:05:12 2017 From: robert at omniti.com (Robert Treat) Date: Fri, 15 Dec 2017 18:05:12 -0500 Subject: [OmniOS-discuss] OmniOS CE AMIs Now Available Message-ID: Howdy! This week we uploaded two new AMI's for OmniOS CE. They are: ami-d390faa9 - OmniOS CE r151022 LTS 20171212 ami-c89df7b2 - OmniOS CE r151024 Stable 20171212 They should be publically available for AWS users in all regions. Cheers! Robert Treat https://omniti.com From paladinemishakal at gmail.com Tue Dec 19 10:44:26 2017 From: paladinemishakal at gmail.com (Lawrence Giam) Date: Tue, 19 Dec 2017 18:44:26 +0800 Subject: [OmniOS-discuss] Problem with BSD Loader and boot mirror Message-ID: Hi All, I have a physical server which I am taking the time to install and test the OmniOS SCE R151022. As with the Grub loader and OmniOS R151014, I use the following steps to setup a boot mirror: 1. Partition a partition on the SSD for the boot mirror. 2. Do the prtvtoc /dev/rdsk/c2t1d0s0 | fmthard -s - /dev/rdsk/c2t0d0s0 3. Attach the partition to the rpool : zpool attach -f rpool c2t1d0s0 c2t0d0s0 4. Wait for the resilver to finish and then reboot the server, ensure it boots ok. 5. After boots ok, run the installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c2t0d0s0 6. Reboot and ensure booting is good. 7. Shutdown and Simulate c2t1d0s0 failure by taking out the SSD. 8. Power up server and the system still boot to OmniOS but with alert that one of the boot mirror is missing. As with the BSD loader and OmniOS R151022, I use the following steps to setup a boot mirror: 1. Partition a partition on the SSD for the boot mirror. 2. Do the prtvtoc /dev/rdsk/c2t1d0s0 | fmthard -s - /dev/rdsk/c2t0d0s0 3. Attach the partition to the rpool : zpool attach -f rpool c2t1d0s0 c2t0d0s0 4. Wait for the resilver to finish and then reboot the server, ensure it boots ok. 5. After boots ok, run bootadm install-bootloader 6. Reboot and ensure booting is good. 7. Shutdown and Simulate c2t1d0s0 failure by taking out the SSD. 8. Power up server and the system boots with the following message: Loading complete Consoles: internal video/keyboard BIOS drive C: is disk 0 BIOS drive D: is disk 1 ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool rpool ZFS: i/o error - all block copies unavailable ZFS: pool tankAAA is not supported BIOS 608kB/1983056kB available memory illumos/x86 ZFS enabled bootstrap loader, Revision 1.1 ZFS: can't find pool by guid ZFS: can't find pool by guid loading CORE EXT words loading SEARCH & SEACH-EXT words loading John-Hopkins locals loading MARKER loading ficl O-O extensions loading ficl utility classes loading ficl string class start not found Type '?' for a list of commands, 'help' for more detailed help. ok -------------------------------------------------------------------------------------------------- I have 2 pools - rpool and tankAAA configured but somehow the BSD loader is 1. unable to recognise the boot mirror 2. cannot see the other dataset (eg. tankAAA) Next, I shutdown the server and put back the disk and power up the server again and it is able to boot as before normally. Is my step to do the boot mirror wrong or is there something that I am missing out? Thanks & Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From softwareinforjam at gmail.com Tue Dec 19 20:06:33 2017 From: softwareinforjam at gmail.com (Software Information) Date: Tue, 19 Dec 2017 15:06:33 -0500 Subject: [OmniOS-discuss] Renaming an interface Message-ID: Hi All I tried to rename an interface with the command *dladm rename-link e1000g0 net0* and I got the error *rename operation failed: link busy. *This happens even after I down or disable the interface either with* ifconfig e1000g0* down or *ipadm disable-addr -t e1000g0/v4* How can I work around this issue or is it something I am overlooking? Regards. SI -------------- next part -------------- An HTML attachment was scrubbed... URL: From omnios at citrus-it.net Tue Dec 19 22:27:34 2017 From: omnios at citrus-it.net (Andy Fiddaman) Date: Tue, 19 Dec 2017 22:27:34 +0000 (UTC) Subject: [OmniOS-discuss] Renaming an interface In-Reply-To: References: Message-ID: On Tue, 19 Dec 2017, Software Information wrote: ; Hi All ; I tried to rename an interface with the command *dladm rename-link e1000g0 ; net0* ; and I got the error *rename operation failed: link busy. *This happens even ; after I down or disable the interface either with* ifconfig e1000g0* down ; or *ipadm disable-addr -t e1000g0/v4* ; ; How can I work around this issue or is it something I am overlooking? You will have to delete both the address and the interface via ipadm. For example: ipadm delete-addr e1000g0/v4 ipadm delete-if e1000g0 dladm rename-link e1000g0 net0 ipadm create-if net0 ipadm create-addr -T static -a local=x.x.x.x/xx net0/v4 Regards, Andy -- Citrus IT Limited | +44 (0)333 0124 007 | enquiries at citrus-it.co.uk Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and Wales | Company number 4899123