aports issueshttps://gitlab.alpinelinux.org/alpine/aports/-/issues2019-07-12T14:23:03Zhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/101Startup script broken for dnscache2019-07-12T14:23:03ZChristoffer LeitetStartup script broken for dnscacheThe startup script for dnscache: /etc/init.d/dnscache is broken.
For example, stopping and restarting doesn’t work correctly.
/etc/init.d/dnscache stop
- Stopping dnscache…
- start-stop-daemon: —make-pidfile is only relevant with ...The startup script for dnscache: /etc/init.d/dnscache is broken.
For example, stopping and restarting doesn’t work correctly.
/etc/init.d/dnscache stop
- Stopping dnscache…
- start-stop-daemon: —make-pidfile is only relevant with —start \[!!\]
- ERROR: dnscache failed to stop
A ps aux reveals that the process is still running
*(from redmine: issue id 101, created on 2009-07-29, closed on 2009-07-31)*
* Changesets:
* Revision 4259b276a2df2018458a622e3ceedad38b1c22ec on 2009-07-30T13:07:09Z:
```
main/dnscache: fix init.d script
fixes #101
```Alpine 1.9 betahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/104apk-tools-2.0_pre16 segfaults2019-07-12T14:23:04ZNatanael Copaapk-tools-2.0_pre16 segfaultsthis is just for the record.
fixed here:
http://git.alpinelinux.org/cgit/apk-tools/commit/?id=8e4075e6b1911679ae3da837b5f13fb85c8f01f5
*(from redmine: issue id 104, created on 2009-07-30, closed on 2009-07-30)*
* Relations:
* rel...this is just for the record.
fixed here:
http://git.alpinelinux.org/cgit/apk-tools/commit/?id=8e4075e6b1911679ae3da837b5f13fb85c8f01f5
*(from redmine: issue id 104, created on 2009-07-30, closed on 2009-07-30)*
* Relations:
* relates #100Alpine 1.9 betahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/106dansguardian-2.10.0.3-r3 does not start with blacklist loaded2019-07-12T14:23:05ZLeonardo Arenadansguardian-2.10.0.3-r3 does not start with blacklist loadedAfter having loaded a blacklist, and enabled it in
/etc/dansguardian/lists/bannedsitelist, running
“/etc/init.d/dansguardian start”, it never returns the prompt and squid
is unable to forward requests. Stracing it does not reveal anythin...After having loaded a blacklist, and enabled it in
/etc/dansguardian/lists/bannedsitelist, running
“/etc/init.d/dansguardian start”, it never returns the prompt and squid
is unable to forward requests. Stracing it does not reveal anything
suspect to me.
*(from redmine: issue id 106, created on 2009-07-30, closed on 2010-01-01)*Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/107ACF-dhcp is missing feature on howto configure which nics dhcpd should listen on2019-07-12T14:23:05ZMika HavelaACF-dhcp is missing feature on howto configure which nics dhcpd should listen onYou need some way to configure /etc/conf.d/dhcpd and set the variable
DHCPD\_IFACE in order to specify which nic’s dhcpd should listen on.
*(from redmine: issue id 107, created on 2009-07-30, closed on 2009-12-23)*You need some way to configure /etc/conf.d/dhcpd and set the variable
DHCPD\_IFACE in order to specify which nic’s dhcpd should listen on.
*(from redmine: issue id 107, created on 2009-07-30, closed on 2009-12-23)*Ted TraskTed Traskhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/108acf-openvpn(v0.4.1) displays all files as they would be config-files in the c...2022-01-19T01:35:34ZMika Havelaacf-openvpn(v0.4.1) displays all files as they would be config-files in the config-tabWhen looking at the config-tab for acf-openvpn, you will notice that all
files (“.keep\_net-misc\_openvpn-0”, certificate-files, etc) will get
presented in the list of config-files. This causes some confusion.
One suggestion is to filt...When looking at the config-tab for acf-openvpn, you will notice that all
files (“.keep\_net-misc\_openvpn-0”, certificate-files, etc) will get
presented in the list of config-files. This causes some confusion.
One suggestion is to filter out \*.conf files.
*(from redmine: issue id 108, created on 2009-07-30, closed on 2009-08-19)*Mika HavelaMika Havelahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/109acf-openvpn(v0.4.1) We need a way to start/stop various openvpn processes2019-07-12T14:23:06ZMika Havelaacf-openvpn(v0.4.1) We need a way to start/stop various openvpn processesSeems we don’t have any chance to start/stop/restart the various openvpn
processes by using ACF.
*(from redmine: issue id 109, created on 2009-07-30, closed on 2009-08-19)*Seems we don’t have any chance to start/stop/restart the various openvpn
processes by using ACF.
*(from redmine: issue id 109, created on 2009-07-30, closed on 2009-08-19)*Mika HavelaMika Havelahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/110Broken paths dhcpd2019-07-12T14:23:07ZChristoffer LeitetBroken paths dhcpddhcpd installs default config file in /etc/dchpd.conf
The init script looks for //etc/dhcpd/dhcpd.conf (sic.)
I suggest both paths are changed to /etc/dhcpd/dhcpd.conf
*(from redmine: issue id 110, created on 2009-07-30, closed on 20...dhcpd installs default config file in /etc/dchpd.conf
The init script looks for //etc/dhcpd/dhcpd.conf (sic.)
I suggest both paths are changed to /etc/dhcpd/dhcpd.conf
*(from redmine: issue id 110, created on 2009-07-30, closed on 2009-08-19)*
* Changesets:
* Revision de25f1da2b2c5f49e7917971b2e324cb0773fa30 on 2009-07-31T06:23:23Z:
```
main/dhcp: fix paths to lease files and configs
also
* enable paranoia for -user/-group options
* fix install scripts
* import new init.d script
* add missing dirs
* move dhclient to a separate subpackage
Fixes #110
```https://gitlab.alpinelinux.org/alpine/aports/-/issues/111Alpha 18 does not boot in paravirtualized environment2019-07-12T14:23:08ZHadi SukirmanAlpha 18 does not boot in paravirtualized environmentThe alpha 18 iso image does not boot in a paravirtualized environment
(tested in VMware Workstation 6.5.2).
This is a change from previous versions. It does boot if
paravirtualization is disabled.
*(from redmine: issue id 111, create...The alpha 18 iso image does not boot in a paravirtualized environment
(tested in VMware Workstation 6.5.2).
This is a change from previous versions. It does boot if
paravirtualization is disabled.
*(from redmine: issue id 111, created on 2009-07-31, closed on 2009-08-08)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/114acf-apk-tools not working2019-07-12T14:23:09ZChristoffer Leitetacf-apk-tools not workingI have a hd installed Alpine, and have updated it on the cosole at some
occations. When I tried to use the web interface to install a package
today, I got the following error when clicking System->Packages:
Alpine Configuration Frame...I have a hd installed Alpine, and have updated it on the cosole at some
occations. When I tried to use the web interface to install a package
today, I got the following error when clicking System->Packages:
Alpine Configuration FrameworkApplication error occuredShow Detail
/usr/share/acf/app//apk-tools/apk-model.lua:112: attempt to compare
string with nil stack traceback:
/usr/share/acf/app//apk-tools/apk-model.lua:112: in function
‘upgrade\_available’ /usr/share/acf/app//apk-tools/apk-model.lua:142: in
function </usr/share/acf/app//apk-tools/apk-model.lua:128> (tail call):
? /usr/share/acf/app/acf\_www-controller.lua:436: in function
</usr/share/acf/app/acf_www-controller.lua:357> \[C\]: in function
‘xpcall’ /usr/share/acf/app/acf\_www-controller.lua:357: in function
‘dispatch’ \[string “acf”\]:18: in main chunk
*(from redmine: issue id 114, created on 2009-08-04, closed on 2009-12-23)*Alpine 1.9Ted TraskTed Traskhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/115syslinux.cfg serial console does not work in 1.92019-07-12T14:23:10Zaa latchmsyslinux.cfg serial console does not work in 1.9Tested on alpine-1.9.0\_alpha18.iso.
Using
console=ttyS0,9600
, alpine boots successfully (no call trace). However, the serial console
does not work; it seems /etc/inittab is not automatically updated with
the getty for the serial...Tested on alpine-1.9.0\_alpha18.iso.
Using
console=ttyS0,9600
, alpine boots successfully (no call trace). However, the serial console
does not work; it seems /etc/inittab is not automatically updated with
the getty for the serial console to run. I tried manually running the
serial console (vi /etc/inittab; kill -HUP 1), but there was no serial
console. Running screen I am not able to use the serial port at all.
However, if I remove
console=ttyS0,9600
, the serial console can be used normally. Although /etc/inittab can be
used in a committed apkovl to start the serial console, the boot
messages are not displayed to the serial port in that configuration.
I can attach a dmesg if it may be helpful.
*(from redmine: issue id 115, created on 2009-08-05, closed on 2009-10-09)*
* Changesets:
* Revision 84230ad9e9ed1591a6dfb3794610f469b1ca8385 on 2009-08-20T12:02:08Z:
```
main/mkinitfs: upgrade to 2.0_rc3
fixes #115
```
* Revision 5318c56c869d95eb8899b4dad06cf4563187e545 on 2009-09-02T06:53:52Z:
```
main/linux-grsec: upgrade to 200908311711. fix for serial console
Fixes #115
```Alpine 1.9 betaNatanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/116SQUID - bandwidth traffic control2019-07-12T14:23:11ZalgitbotSQUID - bandwidth traffic controlBandwidth traffic control with squid delay pools enabled.
*(from redmine: issue id 116, created on 2009-08-05, closed on 2009-08-08)*Bandwidth traffic control with squid delay pools enabled.
*(from redmine: issue id 116, created on 2009-08-05, closed on 2009-08-08)*https://gitlab.alpinelinux.org/alpine/aports/-/issues/117Samba Domain join lost after reboot2019-07-12T14:23:11ZalgitbotSamba Domain join lost after rebootJoin domain works fine… in the command line, we join and do
authentication. But if do rebooting the machine, we lost the join.
And in the in the web page the join is not working at all. Message in
Samba/Join Domain/ Unable to find a su...Join domain works fine… in the command line, we join and do
authentication. But if do rebooting the machine, we lost the join.
And in the in the web page the join is not working at all. Message in
Samba/Join Domain/ Unable to find a suitable server for the domain
XXXXXXXXXXXXXXX.
It’s a bug?
*(from redmine: issue id 117, created on 2009-08-06, closed on 2009-09-04)*Alpine 1.9 betahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/118Cannot join samba via web interface2019-07-12T14:23:12ZalgitbotCannot join samba via web interfaceFrom issue \#117, reported by anonymous.
In the in the web page the join is not working at all. Message in
Samba/Join Domain/ Unable to find a suitable server for the domain
XXXXXXXXXXXXXXX.
*(from redmine: issue id 118, created on 20...From issue \#117, reported by anonymous.
In the in the web page the join is not working at all. Message in
Samba/Join Domain/ Unable to find a suitable server for the domain
XXXXXXXXXXXXXXX.
*(from redmine: issue id 118, created on 2009-08-07, closed on 2009-12-23)*Alpine 1.9Ted TraskTed Traskhttps://gitlab.alpinelinux.org/alpine/aports/-/issues/119lbu no longer catches changes to /etc/init.d/; other directories special too?2019-07-12T14:23:12ZNathan Angelacoslbu no longer catches changes to /etc/init.d/; other directories special too?Previously, lbu would back up everything changed in /etc
this included customizations to /etc/init.d/\*
Now, lbu does not back up changes to /etc/init.d/\* scripts, unless you
specifically add them with lbu add
Are there any other dir...Previously, lbu would back up everything changed in /etc
this included customizations to /etc/init.d/\*
Now, lbu does not back up changes to /etc/init.d/\* scripts, unless you
specifically add them with lbu add
Are there any other directories marked as “special” by lbu?
*(from redmine: issue id 119, created on 2009-08-08, closed on 2009-08-11)*Alpine 1.9 betaTimo TeräsTimo Teräshttps://gitlab.alpinelinux.org/alpine/aports/-/issues/120dnscache doesn't work on startup (1.9.0beta2)2019-07-12T14:23:14ZNathan Angelacosdnscache doesn't work on startup (1.9.0beta2)Weird problem with dnscache; it is running on 127.0.0.1; and is set to
send requests out the default gateway (standard)
1. echo “nameserver 127.0.0.1” &gt;/etc/resolv.conf
2. echo “RESOLV\_CONF=‘no’” &gt;/etc/udhcpc/udhcp.conf
3. rc-...Weird problem with dnscache; it is running on 127.0.0.1; and is set to
send requests out the default gateway (standard)
1. echo “nameserver 127.0.0.1” >/etc/resolv.conf
2. echo “RESOLV\_CONF=‘no’” >/etc/udhcpc/udhcp.conf
3. rc-update add dnscache
4. ping -c 1 www.google.com
(works fine)
<reboot>
\#ping -c 1 www.google.com
— fails after a very long time; no DNS resolution is possible
\#apk add djbdns
\#dnsq A \[any address\] 127.0.0.1
— will fail
doing a tcpdump on 127.0.0.1 shows the request going to 127.0.0.1; but
no response.
**however**, after logging into the server, doing a:
1. /etc/init.d/dnscache restart
— makes all DNS requests work.
Tried adding a delay in the /etc/init.d/dnscache start script; tried
changing the internet facing interface from dhcp to static; no effect.
DNSCACHE does not work until it is restarted.
Any ideas?
*(from redmine: issue id 120, created on 2009-08-08, closed on 2009-08-19)*
* Changesets:
* Revision 0b2149a1ec7b4881ed69cbc8206e3be153b28e39 on 2009-08-08T16:46:53Z:
```
main/djbdns: added net dependency in initd scripts
fixes #120
```
* Revision 6740d61d3640a7e253d6772364ca83dd82a78a57 on 2009-08-09T13:25:04Z:
```
main/djbdns: provide random seed to dnscache
fixes #120
Thanks to Nathan for solving this.
```Alpine 1.9 betaNatanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/121sysklogd is missing, starts late2019-07-12T14:23:15ZTimo Terässysklogd is missing, starts latesysklogd package is missing from 1.9.0\_beta2 iso, even though it’s in
main aports.
also, it seems that the init.d dependencies could be fine tuned as it
starts pretty late in the startup sequence. i had it in ‘boot’ rc
category and it ...sysklogd package is missing from 1.9.0\_beta2 iso, even though it’s in
main aports.
also, it seems that the init.d dependencies could be fine tuned as it
starts pretty late in the startup sequence. i had it in ‘boot’ rc
category and it started after a lot of other components.
*(from redmine: issue id 121, created on 2009-08-08, closed on 2009-08-19)*
* Changesets:
* Revision 6ed51d98e5a2bb27277cbefb185e62fe657ee16b on 2009-08-09T14:22:48Z:
```
main/sysklogd,busybox-initscripts: start system logger before network
fixes #121
```Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/122SA_SIGINFO signal handling is broke in 1.9.0-beta22019-07-12T14:23:15ZTimo TeräsSA_SIGINFO signal handling is broke in 1.9.0-beta2The kernel is unable to send signals with SA\_SIGINFO. This effectively
breaks all system with padlock, as this is used in openssl padlock
sha1/sha256 acceleration code.
See also:
http://grsecurity.net/pipermail/grsecurity/2009-August...The kernel is unable to send signals with SA\_SIGINFO. This effectively
breaks all system with padlock, as this is used in openssl padlock
sha1/sha256 acceleration code.
See also:
http://grsecurity.net/pipermail/grsecurity/2009-August/000968.html
http://forums.grsecurity.net/viewtopic.php?f=3&t=2173
*(from redmine: issue id 122, created on 2009-08-08, closed on 2009-08-09)*Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/123dansguardian: wrong permissions on /var/log/dansguardian2019-07-12T14:23:16ZStephen Mundansguardian: wrong permissions on /var/log/dansguardianWrong permissions on directory for logfiles.
Create post-install script to solve this.
*(from redmine: issue id 123, created on 2009-08-09, closed on 2009-08-19)*
* Changesets:
* Revision fdd0312a868bdb5256940eb0a028a439211dc10d on...Wrong permissions on directory for logfiles.
Create post-install script to solve this.
*(from redmine: issue id 123, created on 2009-08-09, closed on 2009-08-19)*
* Changesets:
* Revision fdd0312a868bdb5256940eb0a028a439211dc10d on 2009-08-10T06:15:50Z:
```
main/dansguardian: set permissions on /var/log/dansguardian
fixes #123
```Alpine 1.9Natanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/128postinstall depmod2019-07-12T14:23:17Ziilluzion _postinstall depmoda postinstall depmod is needed
Example:
——
\# apk add iscsitarget-grsec
Installing iscsitarget-grsec (0.4.17-r5)
\# find /lib/modules/ -iname “**iscsi**”
…
/lib/modules/2.6.30.4-grsec/kernel/iscsi/iscsi\_trgt.ko
\# modprobe...a postinstall depmod is needed
Example:
——
\# apk add iscsitarget-grsec
Installing iscsitarget-grsec (0.4.17-r5)
\# find /lib/modules/ -iname “**iscsi**”
…
/lib/modules/2.6.30.4-grsec/kernel/iscsi/iscsi\_trgt.ko
\# modprobe iscsi\_trgt
modprobe: module iscsi\_trgt not found
bsna-beta-test:~\# modprobe
/lib/modules/2.6.30.4-grsec/kernel/iscsi/iscsi\_trgt.ko
\# depmod
\# modprobe iscsi\_trgt
\# lsmod | grep iscsi\_trgt
iscsi\_trgt 48612 0
——-
*(from redmine: issue id 128, created on 2009-08-11, closed on 2009-08-19)*
* Changesets:
* Revision d03ad6f9292bdc62226897db4c93e9a435cbe2f7 on 2009-08-18T19:46:42Z:
```
main/busybox: we need both .post-install and trigger
fixes #128
```Alpine 1.9 betaNatanael CopaNatanael Copahttps://gitlab.alpinelinux.org/alpine/aports/-/issues/130grossd initscript fault2019-07-12T14:23:18ZDuane Hughesgrossd initscript faultRestarting grossd with /etc/init.d/grossd restart fails with
start-stop-daemon: /usr/sbin/grossd is already running
start / stop / start works
stop / restart works
start / restart fails
Most likely error with stop in the restart(...Restarting grossd with /etc/init.d/grossd restart fails with
start-stop-daemon: /usr/sbin/grossd is already running
start / stop / start works
stop / restart works
start / restart fails
Most likely error with stop in the restart() function
*(from redmine: issue id 130, created on 2009-08-12, closed on 2009-08-13)*
* Changesets:
* Revision d7c0aed5ab029a04cd60356126d7feede60bfc0a on 2009-08-13T11:54:52Z:
```
main/gross: init.d script fix
we stop the daemon using --exec rather than pidfile. This is to make
sure that all threads (when using linuxthreads) are gone when restarting.
fixes #130
```Alpine 1.9 betaNatanael CopaNatanael Copa