Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 27 23:44

    YanChii on master

    workaround new bootparams varia… (compare)

  • Jan 25 16:02

    YanChii on new_release_20190117

    fixed boot.manifest (compare)

  • Jan 25 16:00

    YanChii on new_release_20190117

    fixed manifest (compare)

  • Jan 25 15:42

    YanChii on new_release_20190117

    OS-7436 vminfod can be overwhel… OS-6795 illumos-joyent build to… OS-7488 vm delete fails after O… and 8 more (compare)

  • Jan 25 15:39

    YanChii on master

    removed VM.js (TSC workaround n… (compare)

  • Jan 25 15:34

    YanChii on master

    moved postboot-rc manifests (compare)

  • Jan 25 15:33

    YanChii on merge-sysinfo

    (compare)

  • Jan 25 15:33

    YanChii on master

    merge sysinfo upstream changes (compare)

  • Jan 25 15:33
    YanChii closed #10
  • Jan 25 14:46

    YanChii on new_release_20190103

    updated boot copyright year (compare)

  • Jan 23 13:48

    YanChii on master

    allow consistently reexecute he… (compare)

  • Jan 23 13:48
    YanChii closed #119
  • Jan 23 13:46
    YanChii synchronize #385
  • Jan 22 21:58
    YanChii synchronize #384
  • Jan 22 21:43
    YanChii synchronize #384
  • Jan 22 19:58
    YanChii synchronize #385
  • Jan 21 09:50

    dn0 on master

    Fixed links to issues (compare)

  • Jan 21 09:08
    YanChii synchronize #385
  • Jan 21 09:02
    YanChii review_requested #385
  • Jan 21 09:02
    YanChii milestoned #385
witte1000
@witte1000
Ja de kleine server is een server die boot vanaf disk, op deze server staat dan de PXE Zone die dan dient om de grote server op te booten en alle andere toekomstige nodes ..
klebed
@klebed
Eine dutch sprache Übungen! Wunderbar! %)))))
Jan Poctavek
@YanChii
@/all to address rpm conflicts, I've just pushed a patchlevel version for updates v4.2.1
if you are already on v4.2, you don't need to upgrade
if you still experience appliance upgrade problems, please let us know
outsider01
@outsider01
[update update]
I upgraded my platform and after that it seems that all errors and DNS warnings from zabbix have disappeared.
So all is fine now!
[/update update]
Jan Poctavek
@YanChii
cool
Jan Poctavek
@YanChii
FYI we have just released CentOS 8 KVM image
FilipFrancis
@FilipFrancis
Nice
klebed
@klebed

FYI we have just released CentOS 8 KVM image

Any chance for Ubuntu/Debian?

Jan Poctavek
@YanChii
@klebed there is a chance but I need help. The CentOS image is installed by kickstart. If you could tell me the kernel boot loader parameters and some basic conf that can be used for automated install of Debian (or Ubuntu), I can do the rest.
the kernel parameters are passed to qemu as qemu_extra_opts together with -kernel and -initrd
like this https://github.com/erigones/esdc-factory/blob/master/ansible/vars/build/vm/base-centos-8-kvm.yml#L17
klebed
@klebed
I doubt I'd have time soon, but I'll try to look into this. I guess 'casper' could be a word we looking for, or debootstrap... Joyent making it's images somehow.
Jan Poctavek
@YanChii
joyent is creating iso and then install it from that… I don't like that approach because it's too manual
https://github.com/joyent/mi-debian
outsider01
@outsider01
anybody here?
@YanChii ??
@YanChii are you here?
i rebooted my server today because i needed to change some UTP wires at home. Now the server boots and halt after the Danube cloud prompt.
outsider01
@outsider01
hmz, sorry . it was a semi false alarm.
The system started and i let it autoboot. For some reason the boot of Danube didn't start danube but in stead said it missed a boot thing? I got a prompt and after pressing "?" i got a lot of options, but i thought "reboot" was the best thing to choose from the list. So i typed reboot, the system rebooted and after that it started as usual. I forgot to take screenshots of the strange boot sequence, so I can't tell what went wrong any further.
Jan Poctavek
@YanChii
@outsider01 if you experience something like that again, let us know
the behavior like this can be achieved for example by hitting Esc during loader prompt… any chance of keyboard miss-type?
and i think Esc will return also back to loader screen
outsider01
@outsider01
i was connected to the "prompt" via the ILO console. It was running free (browser tab not active) during boot, so i don't think i can have hit ESC. But in my case you can never be 100% sure.
I was turning 8 bit colors when it happened because I thought my whole server was unrepairable. And this always happens to remind me I need to create backups.
Jan Poctavek
@YanChii
don't forget to backup also admin VMs for such cases :)
tanhueco
@tanhueco
Is there any way to pull answers.json (from /private/answers.json) from an existing install?
Jan Poctavek
@YanChii
@tanhueco Hi and welcome :)
install does not create answers.json as for example centos kickstart
but you can fill the information from /usbkey/config
outsider01
@outsider01
Small update: Since the update to 4.2 is see a higher energy consumption of my server and slower performance of my CentOS VMs.
average energy consumption before the update was approx. 85 Watts, now it is almost 100Watts.
outsider01
@outsider01
what does this mean:
=WARNING REPORT==== 16-Nov-2019::17:02:33 ===
closing AMQP connection <0.30312.18> (127.0.0.1:49200 -> 127.0.0.1:5672):
connection_closed_abruptly
outsider01
@outsider01
One of my Ubuntu VM's has major problems with the clock:
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:22:13 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:22:18 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:22:19 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:22:20 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:36:58 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:36:59 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:36:22 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:36:24 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:36:25 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:37:04 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:37:18 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:37:57 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ date
Sat Nov 16 18:27:06 UTC 2019
ubuntu@alfresco6:/opt/alfresco/logs/solr6$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource kvm-clock
time is bouncing back and forth with more then 10 minutes
Jan Poctavek
@YanChii
@outsider01 consumption: I believe this is some change in SmartOS itself… maybe some new spectre fixes
clock: try also hwclock -c
we still don't know if this is something that exists in DC platform or is also present in plain SmartOS
some time ago I have build a DC platform without KVM changes (even thou I can't imagine what should affect it in such way)… you might try it and see if the problem still exists
the other way is of course to boot and try the plain SmartOS from a separate usb stick
outsider01
@outsider01
i checked my KVM VM config and it seemd i had forgotten that i changed some of my KVM's settings.
some of my KVM's had the special cpu_type settings that i tried a couple of months ago. I removed these settings and set cpu_type to "qemu64" only
it looks much better now. althou
outsider01
@outsider01
although any cpu number above 1 is only slowing the VM down instead of progressing it
Jan Poctavek
@YanChii
that's interesting… is it only this VM on this node or a general discovery?
tanhueco
@tanhueco
Maybe a dumb question. How do I force delete a node that is unreachable? I purposely created a node for testing with several VM's in it and I destroyed it. I cannot find a way to delete the node in DC.
Jan Poctavek
@YanChii
@tanhueco It's purposely not available through GUI
you can use api command for that:
./es delete /node/<nodename> -force
if I recall correctly