The officially official Devuan Forum!

You are not logged in.

#1 Re: DIY » What do you think of Docker? » 2021-01-16 16:45:20

Well that was easy smile

debootstrap beowulf beowulf
tar -C beowulf -c . | docker import - beowulf
docker run beowulf cat /etc/os-release

Should be easy to automate.

So do you think we could see an official image?

#2 Re: DIY » What do you think of Docker? » 2020-12-20 12:58:31

Just had a bit of a read up of LXC / LXD and while it looks pretty cool, it seem Canonical are heavily involved!  They ruined Ubuntu for me with their crazy Unity interface. I wonder what direction this is going in!? Looks like LXD is their version of LXC, but they are still "sponsoring" the whole project?

Mmm yeah I was wondering about how much to trust containers, Having and understanding the workings of Devuan on the host for privacy/security/trust reasons and then allowing a black box container to run... hmmm.

Rolling my own sounds like a possible solution. I see there are a few non official Devuan base images. But can we trust any of them? I wonder how I'd make my own, or would it be an idea to encourage an official build?

#3 Re: DIY » What do you think of Docker? » 2020-12-16 12:20:03

Head_on_a_Stick wrote:
bobemoe wrote:

systemd isn't actually inside many containers

Yeah, docker's default image is based on Alpine Linux and that is fundamentally incompatible with systemd because it uses musl libc.

But the ubuntu and debian base images are quite popular which is where I'd expect systemd to try and sneak/force its way in!

Head_on_a_Stick wrote:
bobemoe wrote:

Are there better containers systems to be investigating?

There's systemd-nspawn big_smile

But seriously, how about LXC? I don't actually run any servers though so my opinion is pretty worthless.

Sweet, I'd not heard of this, thanks. I'll research this before going down the (dying?) docker route.

Head_on_a_Stick wrote:

Yes, docker is superfluous and just adds an extra layer to Kubernetes' container system:

https://www.tariqislam.com/posts/kubernetes-docker-dep/

Looks a good read, will have a proper look soon, thanks again smile


bgstack15 wrote:

From what I read, I was under the impression that k8s was removing a specific layer of code that interacts with Docker. You will still be able to use Docker components underneath k8s, because they both use CRI (container runtime interface) protocols. https://news.ycombinator.com/item?id=25280888

Thanks also for another good read. I guess I'm still a way off making a decision!

Think I'll have to have a play with Kubernetes then and LXC. Would these be a good choice to maintain software freedom? And maybe ditch Docker.

#4 DIY » What do you think of Docker? » 2020-12-14 16:41:55

bobemoe
Replies: 9

I'm posting this because I've started using Docker a lot lately, mainly on my Devuan servers, and beginning to on my Devuan desktops at home, and it crossed my mind, "What's the point of running Devuan to avoid systemd, if I'm just going to end up having it in various containers!?"

After a bit of research I found that systemd isn't actually inside many containers, its a pain to do so, and pretty pointless! That gave me hope that Docker could be something good. Containers may even be a reason for packages not to adopt systemd wink

So I'm on the brink of embracing Docker, and I find that kubernetes is deprecating Docker: https://kubernetes.io/blog/2020/12/02/d … nd-docker/

Will Docker take a big hit with this? Is this the right time to be embracing it? Are there better containers systems to be investigating?

Are their reasons genuine or is it sneaky move to force the direction of adoption, similar to how systemd does?

Thoughts? smile

#5 Installation » Getting varnish to work on beowulf » 2020-11-20 10:58:43

bobemoe
Replies: 1

Just upgraded from ascii to beowulf and varnish fails to start with:

Error: Could not get socket 0.0.0.0:6081: Address already in use

The solution is to remove the config check from the init.d script as documented here:
https://github.com/varnishcache/pkg-var … /issues/75

Does this need to be added to devuan's init.d scripts somehow so its included automatically?

Big thanks to everyone big_smile

#6 Re: Installation » Beowulf keyboard missing keystrokes » 2020-07-05 05:35:04

Since noirqdebug the USB/keyboard input is perfect, but I'm hearing glitches on the sound card now and the system seems a bit sluggish, presumably because the IRQ's are being handled differently.

@Head_on_a_Stick I've not tried live yet, I'll give it a go.

#7 Re: Installation » Beowulf keyboard missing keystrokes » 2020-07-04 16:04:52

Looks like adding noirqdebug to kernel cmdline has fixed the issue.  I've suspended 5 times now with no issue.

I also tried acpi=routeirq and pci=msi which did not help.

Strange I found the answer in a 2009 thread about kernel 2.x! Something regressed?

I'll report back if it occurs again.

Software freedom FTW big_smile

#8 Re: Installation » Beowulf keyboard missing keystrokes » 2020-07-04 15:24:03

So it does seem pretty consistent. After 2 suspends the issue returns. I've confirmed this three times. An IRQ16 issue is seen in dmesg upon the issue occurring.

[  155.169229] irq 16: nobody cared (try booting with the "irqpoll" option)
[  155.169238] CPU: 0 PID: 4465 Comm: pm-powersave Not tainted 4.19.0-9-amd64 #1 Debian 4.19.118-2+deb10u1
[  155.169239] Hardware name: Hewlett-Packard HP xw4550 Workstation/0AC8h, BIOS 786F7 v01.07 04/23/2012
[  155.169240] Call Trace:
[  155.169244]  <IRQ>
[  155.169252]  dump_stack+0x66/0x90
[  155.169257]  __report_bad_irq+0x3a/0xb4
[  155.169260]  note_interrupt.cold.9+0xa/0x64
[  155.169263]  handle_irq_event_percpu+0x6d/0x80
[  155.169266]  handle_irq_event+0x3c/0x5c
[  155.169268]  handle_fasteoi_irq+0xa3/0x160
[  155.169271]  handle_irq+0x1f/0x30
[  155.169274]  do_IRQ+0x49/0xe0
[  155.169277]  common_interrupt+0xf/0xf
[  155.169278]  </IRQ>
[  155.169282] RIP: 0010:_cond_resched+0x5/0x30
[  155.169285] Code: 01 eb ba 66 90 bf 01 00 00 00 e8 26 f5 ff ff 65 48 8b 04 25 40 5c 01 00 48 8b 00 a8 08 75 e6 c3 0f 1f 44 00 00 66 66 66 66 90 <65> 8b 05 d4 b9 4e 7a 85 c0 74 08 e8 db 87 9c ff 31 c0 c3 e8 c3 ff
[  155.169286] RSP: 0000:ffffb54b449d7ee0 EFLAGS: 00000202 ORIG_RAX: ffffffffffffffda
[  155.169288] RAX: 0000000000000001 RBX: 0000000000000004 RCX: 0000000000000000
[  155.169289] RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffff945d3503aaf0
[  155.169290] RBP: 00007fe763a9c4ad R08: 0000000000000000 R09: 0000000000000000
[  155.169291] R10: 0000000000000000 R11: 0000000000000000 R12: ffffb54b449d7f58
[  155.169292] R13: ffff945d3503aa80 R14: 0000000000000054 R15: ffff945c7eb21b00
[  155.169297]  __do_page_fault+0x14c/0x4f0
[  155.169300]  ? page_fault+0x8/0x30
[  155.169302]  page_fault+0x1e/0x30
[  155.169304] RIP: 0033:0x55d66372d76a
[  155.169306] Code: 00 00 e8 d9 fe ff ff 66 0f 1f 84 00 00 00 00 00 41 54 49 89 fc 55 53 0f b6 1f 80 fb 5f 74 12 e8 0c 4e ff ff 4c 89 e5 48 8b 00 <f6> 44 58 01 04 74 26 4c 89 e5 0f 1f 40 00 48 83 c5 01 0f b6 5d 00
[  155.169307] RSP: 002b:00007ffd0ba1fac0 EFLAGS: 00010207
[  155.169308] RAX: 00007fe763a9c3e0 RBX: 0000000000000066 RCX: 0000000000000075
[  155.169309] RDX: 0000000000000000 RSI: 000055d6647e7c00 RDI: 000055d6647e93ee
[  155.169310] RBP: 000055d6647e93ee R08: 0000000000000000 R09: 0000000000000010
[  155.169311] R10: fffffffffffffe28 R11: 0000000000000202 R12: 000055d6647e93ee
[  155.169312] R13: 000055d6647e7c00 R14: 000055d6647e7e68 R15: 000055d6647e8aa0
[  155.169314] handlers:
[  155.169341] [<0000000021e5ee98>] usb_hcd_irq [usbcore]
[  155.169366] [<000000002666a161>] ata_bmdma_interrupt [libata]
[  155.169384] [<00000000c654a7e1>] azx_interrupt [snd_hda_codec]
[  155.169385] Disabling IRQ #16

This has enabled me to search further, looks upstream kernel issue, lots of good info here: https://bugzilla.redhat.com/show_bug.cgi?id=474624

#9 Re: Installation » Beowulf keyboard missing keystrokes » 2020-07-04 14:54:10

The issue is back!!  Immediately after resuming from suspend it is happening again. I will reboot and suspend again too see if its consistent...

#10 Re: Installation » Beowulf keyboard missing keystrokes » 2020-07-04 13:25:50

So after watching `top` and digging through some logs and then a reboot the issue seems to have vanished! I'm happy, if not a little confused. I've never seen anything like that before, I've been using Linux for years and Devuan since the start. 

Thanks again all and sorry to bother you hmm

I'll let you know if it reoccurs.

Thoughts still welcome for curiosity sake wink

#11 Re: Installation » Beowulf keyboard missing keystrokes » 2020-07-04 13:13:54

This is not limited to X but also an issue in a real tty1.

#12 Installation » Beowulf keyboard missing keystrokes » 2020-07-04 13:01:19

bobemoe
Replies: 7

I've just upgraded from ascii to beowulf and there seems to be a strange issue with the keyboard.

There seems to be a laggy feeling to the text coming onto the screen, lots of characters are missing and occasionally they come out in the wrong order!

If I type slowly this is not such an issue but I usually type quite fast.

Any thoughts?

As an example I have type this quickly without correcting anything and include the original copy below:

Thanks smile And great work all big_smile

----

I've jsut upgade rom aci to beowulf and tehre seem to be astrnaeg ise with teh jkeyboard.

There em so be aig laggyfeelino the text comin onto the ce, lots of charaters are missin and ocasionalyl they ome out in the wrong orde!

If I type loly this is not sch an isus but I usualy type rpet fast.

An thoughts?

As an exaple I hve type this quickly without corectin aytihng and inclue the rignal copy belo:

Thanks smile And geat wrok al :

#13 Re: Off-topic » The End of Trust » 2020-03-13 17:23:03

Hey everyone.  I just came to do a quick search for "gitea" as I've been using it extensively recently and remember Devuan was looking for git solutions, so thought I'd make sure you'd all heard of it and add my +1. This was the only thread with any real mention so I posted here. How did it go?

Interesting thread too wink +1 as well for uMatrix you get a lot more control than NoScript.

Also to note that Google Recatcha v3 looks like its doing this kind of session recording https://www.fastcompany.com/90369697/go … -dark-side

#14 Re: Documentation » How to get Devuan running on Rackspace. » 2019-09-15 10:44:27

After updating this to ASCII I found a 4-5min boot delay before SSH came up. This was in the boot log / emergency console:

Mon Dec 3 17:02:01 2018: [....] Starting Cloud service: cloud-initCloud-init v. 0.7.9 running 'init' at Mon, 03 Dec 2018 17:01:55 +0000. Up 10.30 seconds.
Mon Dec 3 17:02:01 2018: ci-info: +++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++
Mon Dec 3 17:02:01 2018: ci-info: +--------+------+----------------+---------------+-------+-------------------+
Mon Dec 3 17:02:01 2018: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |
Mon Dec 3 17:02:01 2018: ci-info: +--------+------+----------------+---------------+-------+-------------------+
Mon Dec 3 17:02:01 2018: ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0 | . | . |
Mon Dec 3 17:02:01 2018: ci-info: | lo: | True | . | . | d | . |
Mon Dec 3 17:02:01 2018: ci-info: | eth0: | True | 134.213.210.74 | 255.255.255.0 | . | bc:76:4e:08:29:f1 |
Mon Dec 3 17:02:01 2018: ci-info: | eth0: | True | . | . | d | bc:76:4e:08:29:f1 |
Mon Dec 3 17:02:01 2018: ci-info: | eth1: | True | 10.182.67.40 | 255.255.224.0 | . | bc:76:4e:08:3d:89 |
Mon Dec 3 17:02:01 2018: ci-info: | eth1: | True | . | . | d | bc:76:4e:08:3d:89 |
Mon Dec 3 17:02:01 2018: ci-info: +--------+------+----------------+---------------+-------+-------------------+
Mon Dec 3 17:02:01 2018: ci-info: +++++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++++
Mon Dec 3 17:02:01 2018: ci-info: +-------+---------------+---------------+---------------+-----------+-------+
Mon Dec 3 17:02:01 2018: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
Mon Dec 3 17:02:01 2018: ci-info: +-------+---------------+---------------+---------------+-----------+-------+
Mon Dec 3 17:02:01 2018: ci-info: | 0 | 0.0.0.0 | 134.213.210.1 | 0.0.0.0 | eth0 | UG |
Mon Dec 3 17:02:01 2018: ci-info: | 1 | 10.176.0.0 | 10.182.64.1 | 255.240.0.0 | eth1 | UG |
Mon Dec 3 17:02:01 2018: ci-info: | 2 | 10.182.64.0 | 0.0.0.0 | 255.255.224.0 | eth1 | U |
Mon Dec 3 17:02:01 2018: ci-info: | 3 | 10.208.0.0 | 10.182.64.1 | 255.240.0.0 | eth1 | UG |
Mon Dec 3 17:02:01 2018: ci-info: | 4 | 134.213.210.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U |
Mon Dec 3 17:02:01 2018: ci-info: +-------+---------------+---------------+---------------+-----------+-------+
Mon Dec 3 17:02:01 2018: 2018-12-03 17:01:55,639 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [0/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (
Mon Dec 3 17:02:01 2018: 2018-12-03 17:01:56,645 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [1/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (
Mon Dec 3 17:02:01 2018: 2018-12-03 17:01:57,650 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [2/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (
Mon Dec 3 17:02:01 2018: 2018-12-03 17:01:58,655 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [3/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (
Mon Dec 3 17:02:01 2018: 2018-12-03 17:01:59,660 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [4/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (
Mon Dec 3 17:02:01 2018: 2018-12-03 17:02:00,665 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [5/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:02,677 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [7/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:04,683 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [9/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:06,690 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [11/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:08,697 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [13/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:10,703 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [15/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:13,712 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [18/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:16,720 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [21/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:19,727 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [24/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:22,734 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [27/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:25,741 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [30/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:29,749 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [34/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:05 2018: 2018-12-03 17:02:33,773 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [38/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:06 2018: 2018-12-03 17:02:37,781 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [42/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:06 2018: 2018-12-03 17:02:41,789 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [46/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:06 2018: 2018-12-03 17:02:45,793 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [50/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:06 2018: 2018-12-03 17:02:50,803 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [55/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:06 2018: 2018-12-03 17:02:55,808 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [60/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:03:06 2018: 2018-12-03 17:03:00,822 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [65/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:04:22 2018: 2018-12-03 17:03:05,832 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [70/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:04:22 2018: 2018-12-03 17:03:10,845 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [75/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:04:22 2018: 2018-12-03 17:03:16,859 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [81/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:04:22 2018: 2018-12-03 17:03:22,869 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [87/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:04:22 2018: 2018-12-03 17:03:28,880 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [93/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:04:22 2018: 2018-12-03 17:03:34,890 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [99/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:04:22 2018: 2018-12-03 17:03:40,901 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [105/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:04:22 2018: 2018-12-03 17:03:47,919 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [112/120s]: request error [HTTPConnectionPool(host='134.213.210.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id
Mon Dec 3 17:04:22 2018: 2018-12-03 17:03:54,930 - url_helper.py[WARNING]: Calling 'http://134.213.210.1/latest/meta-data/instance-id' failed [119/120s]: unexpected error [Attempted to set connect timeout to 0.0, but the timeout cannot be set to a value less than or equal to 0.]
Mon Dec 3 17:04:22 2018: 2018-12-03 17:04:01,938 - DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata from ['http://134.213.210.1/latest/meta-data/instance-id'] after 126 seconds
Mon Dec 3 17:05:12 2018: 2018-12-03 17:04:52,009 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [50/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/
Mon Dec 3 17:06:02 2018: 2018-12-03 17:05:43,061 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [101/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data
Mon Dec 3 17:06:02 2018: 2018-12-03 17:06:01,082 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data
Mon Dec 3 17:06:02 2018: 2018-12-03 17:06:02,083 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 120 seconds
Mon Dec 3 17:06:02 2018: ^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Mon Dec 3 17:06:02 2018: [....] Starting OpenBSD Secure Shell server: sshd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
Mon Dec 3 17:06:03 2018: [....] Starting Cloud service: cloud-initCloud-init v. 0.7.9 running 'modules:config' at Mon, 03 Dec 2018 17:06:02 +0000. Up 257.74 seconds.
Mon Dec 3 17:06:03 2018: ^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.

After chatting to rackspace I confirmed that it was safe to disable these services:

This is an issue with cloud-init and the recent update you did. Since we do not use a remote source within cloud-init, it is timing out when it first starts the cloud-init service. Disabling the services you've disabled will not cause any future issues with this server.

update-rc.d cloud-config disable
update-rc.d cloud-final disable
update-rc.d cloud-init disable
update-rc.d cloud-init-local disable

Boot times have now returned to normal smile

#15 Re: Hardware & System Configuration » What tool for software updates + notifications? » 2018-09-24 21:45:01

Yeah I could look into that, not done that before but its such a simple script that it would be a good one to start with smile

Not sure where I'd fork it from? Cant find PointLinux repos, and the link in the source.py links back to a yum version, looks like its already been modified lots! Might it just be worth creating a new repo?

I'll dig out the Devuan packaging guide smile

#16 Re: Hardware & System Configuration » What tool for software updates + notifications? » 2018-09-24 16:19:20

So as MiyoLinux said the icon he used was added manually, so I thought I'd see if any suitable ones already existed, I found:

/usr/share/icons/gnome/48x48/apps/update-manager.png
/usr/share/icons/gnome/48x48/apps/system-software-update.png
/usr/share/icons/gnome/48x48/status/software-update-urgent.png
/usr/share/icons/gnome/48x48/status/software-update-available.png

All available in the gnome-icon-theme package, which was already installed.

I've added the following lines to my post install script to download and configure this manually:

# update manager 
wget http://packages.pointlinux.org/pointlinux/pointlinux/pool/main/p/pointlinux-update-notifier/pointlinux-update-notifier_1.3.2~pointlinux%2bagni1.tar.gz
dpkg -i pointlinux-update-notifier_1.3.2~pointlinux+agni1_all.deb
rm pointlinux-update-notifier_1.3.2~pointlinux+agni1_all.deb
sed -ie 's#/usr/share/icons/PointLinux-Faenza/apps/48/update-notifier.png#/usr/share/icons/gnome/48x48/status/software-update-available.png#' /usr/share/pointlinux/update-notifier/pointlinux-update-notifier.py

Wondering if/how we could get this added to the Devuan repos so I can apt install it rather than wget of a path that may change?

#17 Re: Hardware & System Configuration » What tool for software updates + notifications? » 2018-09-24 12:17:24

Wow that package is really awesome!  When it launches synaptic it uses --non-interactive which will take away all of the confusion and make installing the updates really easy even for the most novice users! smile I think I may start using it myself too.

Many thanks MiyoLinux smile

#18 Hardware & System Configuration » What tool for software updates + notifications? » 2018-09-23 17:49:13

bobemoe
Replies: 17

I maintain Linux installs for a lot of friends/family/clients, and since I can always best support the OS that I'm most familiar with I'm slowly migrating them all over to Devuan.  Most are coming from xubuntu, so its pretty straight forward and from their point of view not much has changed.

The biggest problem is keeping them up to date. The ubuntu style software updater I don't think exists for Debian/Devuan and although Synaptic Package Manager does a good job, but most of my users find it too confusing. Also I don't think it has a notification for pending updates?

Being a CLI kind of guy, this isn't something I've really looked into, so I'm reaching out for anyone who may have suggestions?

I've considered setting up unattended-updates for them so it's all handled in the background, but it would be nice for them to get to say when to do it, so it doesn't use resources when they wanting to do something.

So, any ideas? What do you use?
Thanks :)

#19 Documentation » How to get Devuan running on Rackspace. » 2018-02-01 21:02:41

bobemoe
Replies: 2

It's pretty straight forward. First create a new Debian Jessie server, ssh in and run the following standard method to upgrade to Devuan.

echo -e "deb http://auto.mirror.devuan.org/merged jessie main\ndeb http://auto.mirror.devuan.org/merged jessie-updates main\ndeb http://auto.mirror.devuan.org/merged jessie-security main" > /etc/apt/sources.list
apt-get update && apt-get install devuan-keyring -y --allow-unauthenticated
apt-get update
apt-get dist-upgrade -y
reboot

Congratulations! You now have Devuan running. Log back in and run the following to clean up:

apt-get purge systemd libsystemd0 -y
apt-get autoremove --purge -y
apt-get autoclean

Up until recently this was all that was needed, but nova-agent seem to have dropped support for init systems other than systemd. If you don't create the init script manually, nova-agent won't start on boot. This does not affect reboots of the VM, however if you image it and build another server from the image, on first boot it will not get its new IP address, and, although the build succeeds after an hour, it still will not have network access.

NOTE! The following is a bit of a ugly hack. I just took the startup line from the latest systemd service file and popped it into the start function of an old init.d script from before they were removed. It works, but I have not written the stop function. I'm not sure the implications of this. I hope to update to a better version soon. Feel free to post suggestions smile

Create the file /etc/init.d/nova-agent with the following:

#!/bin/sh

# vim: tabstop=4 shiftwidth=4 softtabstop=4
#
#  Copyright (c) 2011 Openstack, LLC.
#  All Rights Reserved.
#
#     Licensed under the Apache License, Version 2.0 (the "License"); you may
#     not use this file except in compliance with the License. You may obtain
#     a copy of the License at
#
#          http://www.apache.org/licenses/LICENSE-2.0
#
#     Unless required by applicable law or agreed to in writing, software
#     distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
#     WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
#     License for the specific language governing permissions and limitations
#     under the License.
#
# nova-agent	Startup script for OpenStack nova guest agent
#
# RedHat style init header:
#
# chkconfig: 2345 15 85
# description: nova-agent is an agent meant to run on unix guest instances \
#              being managed by OpenStack nova.  Currently only works with \
#              Citrix XenServer for manipulating the guest through \
#              xenstore.
# processname: nova-agent
# pidfile: /var/run/nova-agent.pid
#
# LSB style init header:
#
### BEGIN INIT INFO
# Provides: Nova-Agent
# Required-Start: $remote_fs $syslog xe-linux-distribution
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start nova-agent at boot time
# Description: nova-agent is a guest agent for OpenStack nova.
### END INIT INFO

# Source function library.
if [ -e "/etc/rc.d/init.d/functions" ]
then
  . /etc/rc.d/init.d/functions
fi

do_start() {
  /usr/bin/nova-agent -o /var/log/nova-agent.log -l info
}

do_stop() {
  echo "TODO: fixme!"
}

SCRIPTNAME=$0

case "$1" in
  start)
    do_start
    ;;
  stop)
    do_stop
    ;;
  restart)
    do_stop
    do_start
    ;;
  *)
    echo "Usage: $SCRIPTNAME {start|stop|restart}" >&2
    exit 3
    ;;
esac

Then add it to startup with:

chmod +x /etc/init.d/nova-agent
update-rc.d nova-agent defaults

#20 Re: Installation » firmware? » 2017-01-30 21:42:58

I can confirm this too, my wifi was not detected on beta2 whereas it was on beta1. This leaves the system networkless after an install. I followed the steps above to get online and setup the correct mirror, fairly straightforward for the experienced de(bi|vu)an user but certainly not a good start for the novice or newcomer or the NETINST.

Looking at issue #90 and #91 I see neither have had any attention or been tagged for the RC.

I tried to tag them but I don't think I have permission? All I managed to do was add one as a "Todo" but I'm not really sure what this means!? Now I only have the option to mark it "Done".  Is this a personal Todo list or am I messing up the job status?

Just wanted to make sure this gets the attention it needs, I'd hate it to be overlooked for the RC.

#21 Re: Forum Feedback » SEO / URLs » 2016-12-31 09:50:48

Yep, confirmed, looking good smile

#22 Re: Forum Feedback » SEO / URLs » 2016-12-29 12:19:35

Ok cool, glad all is well, good to see the site serving up again on the www.  Guess it's on of my pet fears to see a site not responding hmm

I have done a fair bit with DNS/hosting/server config/web apps etc so if you need a hand with anything in that area, just give me a shout! smile

#23 Re: Forum Feedback » SEO / URLs » 2016-12-27 09:41:22

I've just been doing some reading about DNS and it confirmed my suspicions, seems its not possible to set up a redirect with NS/DNS. Your domain registrar may offer redirect features but they will have to have a webserver and route your HTTP requests via that to preform the redirect.. an unnecessary extra step.

I'd recommend putting DNS back how it was and using nginx config to achieve everything.

Apologies again for causing trouble.

Refs on DNS redirect:
https://productforums.google.com/forum/ … WMDud30RWQ
http://webmasters.stackexchange.com/que … eeping-the
http://serverfault.com/questions/385893 … cords-only

#24 Re: Forum Feedback » SEO / URLs » 2016-12-27 09:23:18

Secondly the link assumes we use Apache for our web-server. We don't and instead went with nginx. However I went ahead and modified the nameserver to redirect www.dev1galaxy.org to dev1galaxy.org so this issue should be fixed soon (if it doesn't I've obviously screwed something up and I'll have to fix it tongue)

I'm not sure if its possable to set up a 301 redirect at the nameserver level? The www site is failing to connect for me now. I'm so sorry to have instigated this and caused an issue I was trying to prevent! hmm I'm sure it'll yield benefits in the long run.

I've worked on a few nginx servers too so have tinkered with it a little. You can set up a redirect for nginx:
http://stackoverflow.com/questions/7947 … r-11733363

This hasn't been updated to be compatible with our version of FluxBB, which is version 1.5.10. Further I'm unsure if this really is that big of an issue though...

Aww shame the module is out of date. I've not used fluxbb so it was just something I spotted after a quick search.  I agree keywords in URLs probably isnt a big boost any more as it used to be. The main benefit I saw from that module was that it removed the index.php from the front page. As we stand at the moment the same content is accessible from https://dev1galaxy.org/index.php and https://dev1galaxy.org (with www removed its only 2 URLs not 4 combinations) Again this could probably be fixed with an nginx redirect, or maybe there is a simpler module to do it that doesn't add keywords to URLs. Maybe its not such a big deal either, its only the front page, now the www issue is being fixed there is only one URL for each topic, which are the main content areas.

#25 Forum Feedback » SEO / URLs » 2016-12-26 20:44:27

bobemoe
Replies: 8

Just having a browse round the forums, great to see it gaining momentum! smile

I'm a bit worried it might take a SEO hit because of duplicate content issues.  Specifically the www and index.php issues described here:
http://www.ragepank.com/articles/3/prev … e-content/

Additionally when accessing the forum with www. in the URL, the login cookies aren't shared across the subdomain. Meaning I can be logged in on www. and logged out on the non-www domain of the same site. Potential here for usability confusion, especially if search engines index both "versions" of the site and I arrive from a link different from that which I have open in another tab. The above link explains how to add a rewrite rule to redirect www to non-www or visa versa which removes these concerns.

This fluxbb module looks like it would solve the index.php issue.
https://fluxbb.org/resources/mods/fluxr … ssentials/
It also adds keywords to the URLs, used to be good SEO practice, though current thoughts are that it's not so necessary these days:
http://webmasters.stackexchange.com/que … -redundant
If you do use that module, I'd add it to a staging or dev site first and make sure the old URLs are correctly 301 redirected to the new ones, or it could cause a SEO hit to any pages that have already been indexed.  Best to do it while the site is small and new rather than further down the line though.

I'm no SEO expert, more the dev that ends up implementing the SEO changes on the server, so I've cleaned up situations like this many times, and happy to help or give any further thoughts, or even test out the module on staging site if needed?

Board footer

Forum Software