astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] Setting up Geoblocking on Astlinux

[Lonnie A. <li...@lo...>]

Michael,

As your original question asked, you wanted to block all countries except one or two.

I suppose you could be clever and block all by default in /mnt/kd/blocklists/blocked-hosts.netset
--
0.0.0.0/1
128.0.0.0/1
--
and then use the whitelist to add your allowed countries .netset's 

BTW, I have not tried this !

But a more elegant method would be to generate a custom block-all-except-xx-yy.netset on an external host for your custom use.

The FireHol project uses a handy script "iprange" (should be on Debian)
https://github.com/firehol/iprange/wiki

The "exclude" mode does a compliment of the added file, so in theory (not tested) you could start with this file:
--
0.0.0.0/1
128.0.0.0/1
--
and then "exclude" what countries you want to allow to generate a block-all-except-xx-yy.netset file.

The iprange command has a bunch of other unique and useful features.  Though I'm not sure if it applies to AstLinux enough to be included ?

Lonnie



> On Aug 19, 2019, at 7:05 PM, Michael Knill <mic...@ip...> wrote:
> 
> Thanks Lonnie for the info.
> 
> Regards
> Michael Knill
> 
> On 20/8/19, 12:30 am, "Lonnie Abelbeck" <li...@lo...> wrote:
> 
> 
> 
>> On Aug 19, 2019, at 1:17 AM, Michael Knill <mic...@ip...> wrote:
>> 
>> Hi all
>> 
>> Is there an easy way to set up Geoblocking on the firewall?
>> I would want to open up a couple of countries and block everything else.
>> 
>> Regards
>> Michael Knill
> 
>    I would start here:
> 
>    Firewall External Block List
>    https://doc.astlinux-project.org/userdoc:tt_firewall_external_block_list
> 
>    I would argue it is better to block attackers/threats rather than countries.  Take a look at the "Country Map" for firehol_level1:
> 
>    http://iplists.firehol.org/?ipset=firehol_level1
> 
>    I personally use this cron entry to update threat blocklists two times a day:
>    --
>    ## Reload firewall blocklists
>    45 05,15 * * * reload-blocklist-netset /mnt/kd/blocklists firehol_level1 firehol_webclient spamhaus_dropv6 >/dev/null 2>&1
>    --
>    (please change the time cron slightly if you copy-paste)
> 
>    I also manually create a /mnt/kd/blocklists/whitelist.netset file to make sure critical upstream HOST/CIDR's never get blocked ... DNS, NTP, SIP providers, etc. .
> 
>    BTW, I do get occasional false positives for HTTP/HTTPS outbound with the firehol_webclient blocklist since one bad actor on a shared server results in blocking the shared server's IP for a period of time.
> 
>    BTW, for years the "voipbl" blocklist worked well, but lately there has been too many false-positives to recommend.
> 
>    Back to your original question, blocking countries ... create your own /mnt/kd/blocklists/block-country-xx.netset files, DDG'ing I found a couple sites offering free, *.netset compatible file formats:
> 
>    http://www.ipdeny.com/ipblocks/
> 
>    https://www.countryipblocks.net/acl.php
>    (Select Format: CIDR)
> 
>    I'm sure there are other Geo-blocklists sources as well.
> 
>    Note the Geo-blocklists do not need to be updated nearly as often as the threat blocklists do, I'm not sure but ever month (or longer) is probably enough, depending on how accurate you want it.
> 
>    Lonnie
> 
> 
> 
> 
>    _______________________________________________
>    Astlinux-users mailing list
>    Ast...@li...
>    https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
>    Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Setting up Geoblocking on Astlinux

[Michael K. <mic...@ip...>]

Thanks Lonnie for the info.

Regards
Michael Knill

On 20/8/19, 12:30 am, "Lonnie Abelbeck" <li...@lo...> wrote:

    
    
    > On Aug 19, 2019, at 1:17 AM, Michael Knill <mic...@ip...> wrote:
    > 
    > Hi all
    >  
    > Is there an easy way to set up Geoblocking on the firewall?
    > I would want to open up a couple of countries and block everything else.
    >  
    > Regards
    > Michael Knill
    
    I would start here:
    
    Firewall External Block List
    https://doc.astlinux-project.org/userdoc:tt_firewall_external_block_list
    
    I would argue it is better to block attackers/threats rather than countries.  Take a look at the "Country Map" for firehol_level1:
    
    http://iplists.firehol.org/?ipset=firehol_level1
    
    I personally use this cron entry to update threat blocklists two times a day:
    --
    ## Reload firewall blocklists
    45 05,15 * * * reload-blocklist-netset /mnt/kd/blocklists firehol_level1 firehol_webclient spamhaus_dropv6 >/dev/null 2>&1
    --
    (please change the time cron slightly if you copy-paste)
    
    I also manually create a /mnt/kd/blocklists/whitelist.netset file to make sure critical upstream HOST/CIDR's never get blocked ... DNS, NTP, SIP providers, etc. .
    
    BTW, I do get occasional false positives for HTTP/HTTPS outbound with the firehol_webclient blocklist since one bad actor on a shared server results in blocking the shared server's IP for a period of time.
    
    BTW, for years the "voipbl" blocklist worked well, but lately there has been too many false-positives to recommend.
    
    Back to your original question, blocking countries ... create your own /mnt/kd/blocklists/block-country-xx.netset files, DDG'ing I found a couple sites offering free, *.netset compatible file formats:
    
    http://www.ipdeny.com/ipblocks/
    
    https://www.countryipblocks.net/acl.php
    (Select Format: CIDR)
    
    I'm sure there are other Geo-blocklists sources as well.
    
    Note the Geo-blocklists do not need to be updated nearly as often as the threat blocklists do, I'm not sure but ever month (or longer) is probably enough, depending on how accurate you want it.
    
    Lonnie
    
    
    
    
    _______________________________________________
    Astlinux-users mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-users
    
    Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
    

Re: [Astlinux-users] Setting up Geoblocking on Astlinux

[Lonnie A. <li...@lo...>]

> On Aug 19, 2019, at 1:17 AM, Michael Knill <mic...@ip...> wrote:
> 
> Hi all
>  
> Is there an easy way to set up Geoblocking on the firewall?
> I would want to open up a couple of countries and block everything else.
>  
> Regards
> Michael Knill

I would start here:

Firewall External Block List
https://doc.astlinux-project.org/userdoc:tt_firewall_external_block_list

I would argue it is better to block attackers/threats rather than countries.  Take a look at the "Country Map" for firehol_level1:

http://iplists.firehol.org/?ipset=firehol_level1

I personally use this cron entry to update threat blocklists two times a day:
--
## Reload firewall blocklists
45 05,15 * * * reload-blocklist-netset /mnt/kd/blocklists firehol_level1 firehol_webclient spamhaus_dropv6 >/dev/null 2>&1
--
(please change the time cron slightly if you copy-paste)

I also manually create a /mnt/kd/blocklists/whitelist.netset file to make sure critical upstream HOST/CIDR's never get blocked ... DNS, NTP, SIP providers, etc. .

BTW, I do get occasional false positives for HTTP/HTTPS outbound with the firehol_webclient blocklist since one bad actor on a shared server results in blocking the shared server's IP for a period of time.

BTW, for years the "voipbl" blocklist worked well, but lately there has been too many false-positives to recommend.

Back to your original question, blocking countries ... create your own /mnt/kd/blocklists/block-country-xx.netset files, DDG'ing I found a couple sites offering free, *.netset compatible file formats:

http://www.ipdeny.com/ipblocks/

https://www.countryipblocks.net/acl.php
(Select Format: CIDR)

I'm sure there are other Geo-blocklists sources as well.

Note the Geo-blocklists do not need to be updated nearly as often as the threat blocklists do, I'm not sure but ever month (or longer) is probably enough, depending on how accurate you want it.

Lonnie

[Astlinux-users] Setting up Geoblocking on Astlinux

[Michael K. <mic...@ip...>]

Hi all

Is there an easy way to set up Geoblocking on the firewall?
I would want to open up a couple of countries and block everything else.

Regards
Michael Knill

Re: [Astlinux-users] Block specific outgoing number.

[Fernando F. <ffu...@da...>]

As we have it right now I get:

Executing [NUMBER@phones:2] GotoIf("SIP/PHONEID-00000a9b", "0?lenny2") in new stack

And does nothing. Any ideas?

Is there a better way to do this? Maybe a password like David did?
David can you share your code?

TIA!

Regards,


--
Fernando Fuentes
ffu...@tx...
http://www.txweather.org



On Sat, Aug 17, 2019, at 11:31 PM, Fernando Fuentes wrote:
> Thank you all for the help.
> Is been so long that I touch the dial plan that I am having a hard time remembering lol....
> I just updated to AST 13 from 1.8 not too long ago.... LOL
> 
> Here is what I got and does not seem to do the trick
> 
> [flowroute-outbound]
> exten => _1NXXNXXXXXX,1,Set(TRUNKCHECK=0)
> same => n,Set(PEERCHECK1=flowroute)
> same => n,NoOp(-- ${PEERCHECK1} status: ${SIPPEER(${PEERCHECK1},status)} --)
> same => n,ExecIf($["${SIPPEER(${PEERCHECK1},status):0:2}"="OK"]?Set(TRUNKCHECK=1))
> same => n,GotoIf($[${TRUNKCHECK}=0]?${EXTEN},failover)
> same => n,Set(CALLERID(num)=MYCID)
> same => n,Verbose(0,${CALLERID(num)} is calling ${EXTEN})
> same => n,GotoIf($["${CALLERID(num)}" = "MYKIDSMISTERYGIRLFRIENDAT3AM"]?lenny2)
> same => n,Dial(${FLWRT}/${EXTEN})
> same => n,GotoIf($[${DIALSTATUS}=CHANUNAVAIL]?${EXTEN},failover)
> same => n(failover),Dial(${GSM}/${EXTEN})
> same => n,Hangup()
> exten => _NXXNXXXXXX,1,Goto(1${EXTEN},1)
> exten => 911,1,Set(CALLERID(num)=MYCID)
> same => n,Dial(${VMS}/911)
> same => n,Dial(${GSM}/911)
> same => n,Hangup()
> 
> same => n(lenny2),1,NoOp(Rerouting outbound call...)
> same => n,Set(SENDTO=53669)
> same => n,System(echo "Channel: local/${SENDTO}@from-internal" > /tmp/lenny.call)
> same => n,System(echo "MaxRetries: 0" >> /tmp/lenny.call)
> same => n,System(echo "RetryTime: 3" >> /tmp/lenny.call)
> same => n,System(echo "WaitTime: 30" >> /tmp/lenny.call)
> same => n,System(echo "Context: bridgit" >> /tmp/lenny.call)
> same => n,System(echo "samesion: 4" >> /tmp/lenny.call)
> same => n,System(echo "Priority: 1" >> /tmp/lenny.call)
> same => n,System(mv /tmp/lenny.call /var/spool/asterisk/outgoing)
> 
> Any ideas what I am doing wrong? I am sure is all jacked up lol!
> 
> Thanks!
> --
> Fernando Fuentes
> ffu...@tx...
> http://www.txweather.org
> 
> 
> 
> On Sat, Aug 17, 2019, at 5:57 PM, David Kerr wrote:
>> Well, I don't block individual numbers but I do control outbound international calls. I have a list of permitted country codes in ActionList and I check against those for all calls starting with 00 or 011. If the country code is not in my (comma separated) list then I ask the caller to Authenticate() and if that passes then it is ok to dial. I implemented this years ago when international calls cost way more than they do now. But still its a nice check to have. Premium rate 900 calls might also be good to block (or require a passcode).
>> 
>> David
>> 
>> 
>> 
>> On Sat, Aug 17, 2019 at 6:28 PM Lonnie Abelbeck <li...@lo...> wrote:
>>> 
>>> 
>>> > On Aug 17, 2019, at 4:44 PM, Fernando Fuentes <ffu...@da...> wrote:
>>> > 
>>> > Team,
>>> > 
>>> > I have a blacklist setup and works perfectly fine for incoming.
>>> > I have one number that I want to block outgoing.
>>> > 
>>> > Can I do that? Can I block an outgoing number if it exists in the blacklist?
>>> 
>>> Sure, take a look in your current extensions.conf and see how the inbound handles the blacklist using
>>> --
>>> ${DB_EXISTS(blacklist/${CALLERID(num)}
>>> --
>>> study it and refresh your memory how this works.
>>> 
>>> 
>>> Then, when dialing out, the "${CALLERID(num)" would be replaced with the dialout number passed to your outbound provider. You probably don't need to act on "${DB_RESULT}", just if DB_EXISTS(...) = 0 do nothing.
>>> 
>>> Then create an outbound blacklist gosub to test and act accordingly and call the gosub in the outbound path.
>>> 
>>> Then test.
>>> 
>>> Though, personally I don't see how generally useful this would be.
>>> 
>>> Lonnie
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Astlinux-users mailing list
>>> Ast...@li...
>>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>>> 
>>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>> 
>> _______________________________________________
>> Astlinux-users mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>> 
>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

[Astlinux-users] AstLinux Pre-Release: astlinux-1.3-4325-bca26d

[Lonnie A. <li...@lo...>]

Announcing Pre-Release Version: astlinux-1.3-4325-bca26d

The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.

-- Asterisk 13.23.1 ('13se' version)
   Older than latest Asterisk 13.x version but more tested, built --without-pjproject
   Add json-integer-overflow patches.
   Add security patches for: AST-2019-002, AST-2019-003

-- Asterisk 13.28.0 (version bump) and 16.5.0 (version bump)
   New modules: app_attended_transfer.so, app_blind_transfer.so

-- OpenSSL, major version bump to 1.1.1c, the new LTS series.  The previous 1.0.2 LTS series is EOL at the end of 2019.
   Many packages needed version bumps or patches to be compatible with the new OpenSSL 1.1 API.

-- php, major version bump to 7.2.21, adds OpenSSL 1.1 compatibility

-- Web Interface Edit tab, add support for CodeMirror text editing.
   (Tip: Shift-Reload browser to get the updated CSS style sheet)
   Keyboard Actions: (after clicking text edit area)
   Note: Windows users, use Ctrl instead of Cmd
   Cmd-f -> Find
   Cmd-g -> Find Next
   Cmd-/ -> Toggle Comment
   Cmd-. -> Toggle Comment
   Tab   -> Toggle between "fullscreen" (full-window) mode and normal
   Esc   -> Return to normal, "fullscreen" (full-window) mode off
   More info: https://doc.astlinux-project.org/userdoc:tt_web_interface_edit_codemirror_key_map

-- Fossil, major version bump to 2.9, adds numerous enhancements to the look and feel of the web interface

-- WireGuard VPN, version bump to 0.0.20190702

-- Complete Pre-Release ChangeLog:
https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt

New Documentation Topics:
Edit tab w/CodeMirror Keyboard Mapping -
- https://doc.astlinux-project.org/userdoc:tt_web_interface_edit_codemirror_key_map

Updated Documentation Topics:
Web Interface Display Font -
- https://doc.astlinux-project.org/userdoc:tt_web_interface_font

The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ...

AstLinux Project -> Development
https://www.astlinux-project.org/dev.html

"Development" tab feature for desktop browsers:
Guest VM x86-64bit ISO: Download Pre-Release Guest VM Install ISO (Video Console)


AstLinux Team

Re: [Astlinux-users] Block specific outgoing number.

[Fernando F. <ffu...@da...>]

Thank you all for the help.
Is been so long that I touch the dial plan that I am having a hard time remembering lol....
I just updated to AST 13 from 1.8 not too long ago.... LOL

Here is what I got and does not seem to do the trick

[flowroute-outbound]
exten => _1NXXNXXXXXX,1,Set(TRUNKCHECK=0)
same => n,Set(PEERCHECK1=flowroute)
same => n,NoOp(-- ${PEERCHECK1} status: ${SIPPEER(${PEERCHECK1},status)} --)
same => n,ExecIf($["${SIPPEER(${PEERCHECK1},status):0:2}"="OK"]?Set(TRUNKCHECK=1))
same => n,GotoIf($[${TRUNKCHECK}=0]?${EXTEN},failover)
same => n,Set(CALLERID(num)=MYCID)
same => n,Verbose(0,${CALLERID(num)} is calling ${EXTEN})
same => n,GotoIf($["${CALLERID(num)}" = "MYKIDSMISTERYGIRLFRIENDAT3AM"]?lenny2)
same => n,Dial(${FLWRT}/${EXTEN})
same => n,GotoIf($[${DIALSTATUS}=CHANUNAVAIL]?${EXTEN},failover)
same => n(failover),Dial(${GSM}/${EXTEN})
same => n,Hangup()
exten => _NXXNXXXXXX,1,Goto(1${EXTEN},1)
exten => 911,1,Set(CALLERID(num)=MYCID)
same => n,Dial(${VMS}/911)
same => n,Dial(${GSM}/911)
same => n,Hangup()

same => n(lenny2),1,NoOp(Rerouting outbound call...)
same => n,Set(SENDTO=53669)
same => n,System(echo "Channel: local/${SENDTO}@from-internal" > /tmp/lenny.call)
same => n,System(echo "MaxRetries: 0" >> /tmp/lenny.call)
same => n,System(echo "RetryTime: 3" >> /tmp/lenny.call)
same => n,System(echo "WaitTime: 30" >> /tmp/lenny.call)
same => n,System(echo "Context: bridgit" >> /tmp/lenny.call)
same => n,System(echo "samesion: 4" >> /tmp/lenny.call)
same => n,System(echo "Priority: 1" >> /tmp/lenny.call)
same => n,System(mv /tmp/lenny.call /var/spool/asterisk/outgoing)

Any ideas what I am doing wrong? I am sure is all jacked up lol!

Thanks!
--
Fernando Fuentes
ffu...@tx...
http://www.txweather.org



On Sat, Aug 17, 2019, at 5:57 PM, David Kerr wrote:
> Well, I don't block individual numbers but I do control outbound international calls. I have a list of permitted country codes in ActionList and I check against those for all calls starting with 00 or 011. If the country code is not in my (comma separated) list then I ask the caller to Authenticate() and if that passes then it is ok to dial. I implemented this years ago when international calls cost way more than they do now. But still its a nice check to have. Premium rate 900 calls might also be good to block (or require a passcode).
> 
> David
> 
> 
> 
> On Sat, Aug 17, 2019 at 6:28 PM Lonnie Abelbeck <li...@lo...> wrote:
>> 
>> 
>> > On Aug 17, 2019, at 4:44 PM, Fernando Fuentes <ffu...@da...> wrote:
>>  > 
>>  > Team,
>>  > 
>>  > I have a blacklist setup and works perfectly fine for incoming.
>>  > I have one number that I want to block outgoing.
>>  > 
>>  > Can I do that? Can I block an outgoing number if it exists in the blacklist?
>> 
>>  Sure, take a look in your current extensions.conf and see how the inbound handles the blacklist using
>>  --
>>  ${DB_EXISTS(blacklist/${CALLERID(num)}
>>  --
>>  study it and refresh your memory how this works.
>> 
>> 
>>  Then, when dialing out, the "${CALLERID(num)" would be replaced with the dialout number passed to your outbound provider. You probably don't need to act on "${DB_RESULT}", just if DB_EXISTS(...) = 0 do nothing.
>> 
>>  Then create an outbound blacklist gosub to test and act accordingly and call the gosub in the outbound path.
>> 
>>  Then test.
>> 
>>  Though, personally I don't see how generally useful this would be.
>> 
>>  Lonnie
>> 
>> 
>> 
>>  _______________________________________________
>>  Astlinux-users mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>> 
>>  Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Block specific outgoing number.

[David K. <da...@ke...>]

Well, I don't block individual numbers but I do control outbound
international calls.  I have a list of permitted country codes in
ActionList and I check against those for all calls starting with 00 or
011.  If the country code is not in my (comma separated) list then I ask
the caller to Authenticate() and if that passes then it is ok to dial.  I
implemented this years ago when international calls cost way more than they
do now.  But still its a nice check to have.  Premium rate 900 calls might
also be good to block (or require a passcode).

David



On Sat, Aug 17, 2019 at 6:28 PM Lonnie Abelbeck <li...@lo...>
wrote:

>
>
> > On Aug 17, 2019, at 4:44 PM, Fernando Fuentes <ffu...@da...>
> wrote:
> >
> > Team,
> >
> > I have a blacklist setup and works perfectly fine for incoming.
> > I have one number that I want to block outgoing.
> >
> > Can I do that? Can I block an outgoing number if it exists in the
> blacklist?
>
> Sure, take a look in your current extensions.conf and see how the inbound
> handles the blacklist using
> --
> ${DB_EXISTS(blacklist/${CALLERID(num)}
> --
> study it and refresh your memory how this works.
>
>
> Then, when dialing out, the "${CALLERID(num)" would be replaced with the
> dialout number passed to your outbound provider.  You probably don't need
> to act on "${DB_RESULT}", just if DB_EXISTS(...) = 0 do nothing.
>
> Then create an outbound blacklist gosub to test and act accordingly and
> call the gosub in the outbound path.
>
> Then test.
>
> Though, personally I don't see how generally useful this would be.
>
> Lonnie
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>

Re: [Astlinux-users] Block specific outgoing number.

[Lonnie A. <li...@lo...>]

> On Aug 17, 2019, at 4:44 PM, Fernando Fuentes <ffu...@da...> wrote:
> 
> Team,
> 
> I have a blacklist setup and works perfectly fine for incoming.
> I have one number that I want to block outgoing.
> 
> Can I do that? Can I block an outgoing number if it exists in the blacklist?

Sure, take a look in your current extensions.conf and see how the inbound handles the blacklist using
--
${DB_EXISTS(blacklist/${CALLERID(num)}
--
study it and refresh your memory how this works.


Then, when dialing out, the "${CALLERID(num)" would be replaced with the dialout number passed to your outbound provider.  You probably don't need to act on "${DB_RESULT}", just if DB_EXISTS(...) = 0 do nothing.

Then create an outbound blacklist gosub to test and act accordingly and call the gosub in the outbound path.

Then test.

Though, personally I don't see how generally useful this would be.

Lonnie

[Astlinux-users] Block specific outgoing number.

[Fernando F. <ffu...@da...>]

Team,

I have a blacklist setup and works perfectly fine for incoming.
I have one number that I want to block outgoing.

Can I do that? Can I block an outgoing number if it exists in the blacklist?

Thank You!

Regards,

-- 
Fernando Fuentes
ffu...@tx...
http://www.txweather.org

Re: [Astlinux-users] One of my APU's broke

[Lonnie A. <li...@lo...>]

> So my questions are:
> 	• Is this just an unlucky flash problem or could there be something more sinister?

Your logs seem to show flash issues:
--
kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
kernel: ata1: irq_stat 0x00400000, PHY RDY changed
kernel: ata1: SError: { RecovComm Persist PHYRdyChg 10B8B }
kernel: ata1: hard resetting link
kernel: ata1: SATA link down (SStatus 0 SControl 300)
kernel: ata1: hard resetting link
--
Though your hard reboot forced a e2fsck and seemed to (temporarily ?) fix things.

On my healthy APU2, the "ata1" logs should be minimal:
--
pbx4 ~ # dmesg | grep ata1
[    0.942110] ata1: SATA max UDMA/133 abar m1024@0xfeb25000 port 0xfeb25100 irq 19
[    1.263014] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.268165] ata1.00: ATA-10: SB mSATA SSD, S9FM02.8, max UDMA/133
[    1.272969] ata1.00: 31277232 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    1.279020] ata1.00: configured for UDMA/133
--


> 	• Why did it need to do a Memtest when it rebooted. Is this a BiOS thing?
> 

Judging by the "Memtest86+ 5.01 coreboot" version, that is a part of the coreboot BIOS of the APU2 ... somehow it got triggered, usually a keypress, possibly random noise off the serial cable.

BTW, once Memtest86+ is started to runs forever until the <ESC> or such key is hit.


Not related, but for production I like to comment-out the /etc/rc.modules NIC drivers that are not used.

For the APU2's /etc/rc.modules (edit directly) only the "igb" NIC is needed, you can comment-out the others.

Lonnie

Re: [Astlinux-users] One of my APU's broke

[Lonnie A. <li...@lo...>]

As per here:
https://doc.astlinux-project.org/userdoc:board_pcengines_apu2

The /mnt/kd/sensors.conf file must exist (for lmsensors to start) and #'s are comments.

My APU2's /mnt/kd/sensors.conf is:
--
# libsensors configuration file
# -----------------------------
# PC Engines APU2

# k10temp CPU sensor
chip "k10temp-pci-00c3"

label temp1 "CPU Temp"
--

Test with...

pbx4 ~ # sensors
k10temp-pci-00c3
Adapter: PCI adapter
CPU Temp:     +55.4 C  (high = +70.0 C)
                       (crit = +105.0 C, hyst = +104.0 C)

Lonnie


> On Aug 17, 2019, at 7:25 AM, Michael Knill <mic...@ip...> wrote:
> 
> Thanks Michael. It does look that way.
> 
> Hmm thanks for pointing out the error.
> I realise that I am now confused about sensors.conf for the Jetway NF9HG-2930 & Qotom Q190G4N-S07 & Qotom Q530G6.
> Is the file empty with just comments or does the # mean something?
> 
> # libsensors configuration file
> # -----------------------------
> # Qotom Q530G6
> 
> # coretemp CPU sensor
> 
> 
> Regards
> Michael Knill
> 
> On 17/8/19, 6:48 pm, "Michael Keuter" <li...@mk...> wrote:
> 
> 
>> Am 17.08.2019 um 05:16 schrieb Michael Knill <mic...@ip...>:
>> 
>> Hi Group
>> 
>> I have an APU2 installed running version 1.3.6. Due to a UPS battery change, they powered down the APU but had problems with the system on powerup.
>> Symptoms were that you could not web or SSH into box. Attended site and plugged in a serial cable and found that the flash could not be read or there were errors (logs attached).
>> I rebooted the box and it went into a Memory test for some reason which was taking AGES to complete:
>> 
>> Memtest86+ 5.01 coreboot 001| AMD GX-412TC SOC                              
>> CLK: 998.2MHz  (X64 Mode)   | Pass  4% #
>> L1 Cache:   32K  17824 MB/s | Test 42% ################                       
>> L2 Cache: 2048K   5145 MB/s | Test #5  [Moving inversions, 8 bit pattern]    
>> L3 Cache:  None             | Testing: 1024K - 1920M   1919M of 1919M
>> Memory  : 1919M   1547 MB/s | Pattern:   20202020           | Time:   0:01:08
>> ------------------------------------------------------------------------------
>> Core#: 0 (SMP: Disabled)  |  CPU Temp  | RAM: 666 MHz (DDR3-1333) - BCLK: 100
>> State: - Running...       |    59 C    | Timings: CAS 9-9-10-24 @ 64-bit Mode
>> Cores:  1 Active /  1 Total (Run: All) | Pass:       0        Errors:      0 
>> ------------------------------------------------------------------------------
>> 
>> I got sick of waiting so I rebooted again and it all came up fine.
>> I have attached a file with all the logs from these steps.
>> 
>> The reason I am concerned is that I had another one of my APU boxes running 1.3.6 just lock up for some reason and was also fixed with a reboot. I could not find any logs for that one and it may not be related.
>> So my questions are:
>> 	• Is this just an unlucky flash problem or could there be something more sinister?
>> 	• Why did it need to do a Memtest when it rebooted. Is this a BiOS thing?
> 
>    Hi Michael,
> 
>    to me it looks as the mSATA had an issue. Maybe the APU couldn't boot from the mSATA and ran into memtest (but that is speculation).
>    I would replace the mSATA.
> 
>    BTW: Though unrelated, there was a error message regarding "/etc/sensors3.conf".
>    Error: File /etc/sensors3.conf, line 5: Invalid keyword
> 
>    Mine looks like this:
> 
>    ----
>    # libsensors configuration file
>    # -----------------------------
>    # PC Engines APU2
> 
>    # k10temp CPU sensor
>    ----
> 
>> Thanks all.
>> 
>> Regards
>> Michael Knill
>> <Astlinux error log.txt>
> 
>    Michael
> 
>    http://www.mksolutions.info
> 
> 
> 
> 
> 
>    _______________________________________________
>    Astlinux-users mailing list
>    Ast...@li...
>    https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
>    Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] One of my APU's broke

[Michael K. <mic...@ip...>]

Thanks Michael. It does look that way.

Hmm thanks for pointing out the error.
I realise that I am now confused about sensors.conf for the Jetway NF9HG-2930 & Qotom Q190G4N-S07 & Qotom Q530G6.
Is the file empty with just comments or does the # mean something?

# libsensors configuration file
# -----------------------------
# Qotom Q530G6

# coretemp CPU sensor


Regards
Michael Knill

On 17/8/19, 6:48 pm, "Michael Keuter" <li...@mk...> wrote:

    
    > Am 17.08.2019 um 05:16 schrieb Michael Knill <mic...@ip...>:
    > 
    > Hi Group
    >  
    > I have an APU2 installed running version 1.3.6. Due to a UPS battery change, they powered down the APU but had problems with the system on powerup.
    > Symptoms were that you could not web or SSH into box. Attended site and plugged in a serial cable and found that the flash could not be read or there were errors (logs attached).
    > I rebooted the box and it went into a Memory test for some reason which was taking AGES to complete:
    >  
    > Memtest86+ 5.01 coreboot 001| AMD GX-412TC SOC                              
    > CLK: 998.2MHz  (X64 Mode)   | Pass  4% #
    > L1 Cache:   32K  17824 MB/s | Test 42% ################                       
    > L2 Cache: 2048K   5145 MB/s | Test #5  [Moving inversions, 8 bit pattern]    
    > L3 Cache:  None             | Testing: 1024K - 1920M   1919M of 1919M
    > Memory  : 1919M   1547 MB/s | Pattern:   20202020           | Time:   0:01:08
    > ------------------------------------------------------------------------------
    > Core#: 0 (SMP: Disabled)  |  CPU Temp  | RAM: 666 MHz (DDR3-1333) - BCLK: 100
    > State: - Running...       |    59 C    | Timings: CAS 9-9-10-24 @ 64-bit Mode
    > Cores:  1 Active /  1 Total (Run: All) | Pass:       0        Errors:      0 
    > ------------------------------------------------------------------------------
    >  
    > I got sick of waiting so I rebooted again and it all came up fine.
    > I have attached a file with all the logs from these steps.
    >  
    > The reason I am concerned is that I had another one of my APU boxes running 1.3.6 just lock up for some reason and was also fixed with a reboot. I could not find any logs for that one and it may not be related.
    > So my questions are:
    > 	• Is this just an unlucky flash problem or could there be something more sinister?
    > 	• Why did it need to do a Memtest when it rebooted. Is this a BiOS thing?
    
    Hi Michael,
    
    to me it looks as the mSATA had an issue. Maybe the APU couldn't boot from the mSATA and ran into memtest (but that is speculation).
    I would replace the mSATA.
    
    BTW: Though unrelated, there was a error message regarding "/etc/sensors3.conf".
    Error: File /etc/sensors3.conf, line 5: Invalid keyword
    
    Mine looks like this:
    
    ----
    # libsensors configuration file
    # -----------------------------
    # PC Engines APU2
    
    # k10temp CPU sensor
    ----
     
    > Thanks all.
    >  
    > Regards
    > Michael Knill
    > <Astlinux error log.txt>
    
    Michael
    
    http://www.mksolutions.info
    
    
    
    
    
    _______________________________________________
    Astlinux-users mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-users
    
    Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] One of my APU's broke

[Michael K. <li...@mk...>]

> Am 17.08.2019 um 05:16 schrieb Michael Knill <mic...@ip...>:
> 
> Hi Group
>  
> I have an APU2 installed running version 1.3.6. Due to a UPS battery change, they powered down the APU but had problems with the system on powerup.
> Symptoms were that you could not web or SSH into box. Attended site and plugged in a serial cable and found that the flash could not be read or there were errors (logs attached).
> I rebooted the box and it went into a Memory test for some reason which was taking AGES to complete:
>  
> Memtest86+ 5.01 coreboot 001| AMD GX-412TC SOC                              
> CLK: 998.2MHz  (X64 Mode)   | Pass  4% #
> L1 Cache:   32K  17824 MB/s | Test 42% ################                       
> L2 Cache: 2048K   5145 MB/s | Test #5  [Moving inversions, 8 bit pattern]    
> L3 Cache:  None             | Testing: 1024K - 1920M   1919M of 1919M
> Memory  : 1919M   1547 MB/s | Pattern:   20202020           | Time:   0:01:08
> ------------------------------------------------------------------------------
> Core#: 0 (SMP: Disabled)  |  CPU Temp  | RAM: 666 MHz (DDR3-1333) - BCLK: 100
> State: - Running...       |    59 C    | Timings: CAS 9-9-10-24 @ 64-bit Mode
> Cores:  1 Active /  1 Total (Run: All) | Pass:       0        Errors:      0 
> ------------------------------------------------------------------------------
>  
> I got sick of waiting so I rebooted again and it all came up fine.
> I have attached a file with all the logs from these steps.
>  
> The reason I am concerned is that I had another one of my APU boxes running 1.3.6 just lock up for some reason and was also fixed with a reboot. I could not find any logs for that one and it may not be related.
> So my questions are:
> 	• Is this just an unlucky flash problem or could there be something more sinister?
> 	• Why did it need to do a Memtest when it rebooted. Is this a BiOS thing?

Hi Michael,

to me it looks as the mSATA had an issue. Maybe the APU couldn't boot from the mSATA and ran into memtest (but that is speculation).
I would replace the mSATA.

BTW: Though unrelated, there was a error message regarding "/etc/sensors3.conf".
Error: File /etc/sensors3.conf, line 5: Invalid keyword

Mine looks like this:

----
# libsensors configuration file
# -----------------------------
# PC Engines APU2

# k10temp CPU sensor
----
 
> Thanks all.
>  
> Regards
> Michael Knill
> <Astlinux error log.txt>

Michael

http://www.mksolutions.info

[Astlinux-users] One of my APU's broke

[Michael K. <mic...@ip...>]

Hi Group

I have an APU2 installed running version 1.3.6. Due to a UPS battery change, they powered down the APU but had problems with the system on powerup.
Symptoms were that you could not web or SSH into box. Attended site and plugged in a serial cable and found that the flash could not be read or there were errors (logs attached).
I rebooted the box and it went into a Memory test for some reason which was taking AGES to complete:

Memtest86+ 5.01 coreboot 001| AMD GX-412TC SOC
CLK: 998.2MHz  (X64 Mode)   | Pass  4% #
L1 Cache:   32K  17824 MB/s | Test 42% ################
L2 Cache: 2048K   5145 MB/s | Test #5  [Moving inversions, 8 bit pattern]
L3 Cache:  None             | Testing: 1024K - 1920M   1919M of 1919M
Memory  : 1919M   1547 MB/s | Pattern:   20202020           | Time:   0:01:08
------------------------------------------------------------------------------
Core#: 0 (SMP: Disabled)  |  CPU Temp  | RAM: 666 MHz (DDR3-1333) - BCLK: 100
State: - Running...       |    59 C    | Timings: CAS 9-9-10-24 @ 64-bit Mode
Cores:  1 Active /  1 Total (Run: All) | Pass:       0        Errors:      0
------------------------------------------------------------------------------

I got sick of waiting so I rebooted again and it all came up fine.
I have attached a file with all the logs from these steps.

The reason I am concerned is that I had another one of my APU boxes running 1.3.6 just lock up for some reason and was also fixed with a reboot. I could not find any logs for that one and it may not be related.
So my questions are:

  1.  Is this just an unlucky flash problem or could there be something more sinister?
  2.  Why did it need to do a Memtest when it rebooted. Is this a BiOS thing?

Thanks all.

Regards
Michael Knill

[Astlinux-users] One of my APU's broke

[Michael K. <mic...@ip...>]

Hi Group

I have an APU2 installed running version 1.3.6. Due to a UPS battery change, they powered down the APU but had problems with the system on powerup.
Symptoms were that you could not web or SSH into box. Attended site and plugged in a serial cable and found that the flash could not be read or there were errors (logs attached).
I rebooted the box and it went into a Memory test for some reason which was taking AGES to complete:

Memtest86+ 5.01 coreboot 001| AMD GX-412TC SOC
CLK: 998.2MHz  (X64 Mode)   | Pass  4% #
L1 Cache:   32K  17824 MB/s | Test 42% ################
L2 Cache: 2048K   5145 MB/s | Test #5  [Moving inversions, 8 bit pattern]
L3 Cache:  None             | Testing: 1024K - 1920M   1919M of 1919M
Memory  : 1919M   1547 MB/s | Pattern:   20202020           | Time:   0:01:08
------------------------------------------------------------------------------
Core#: 0 (SMP: Disabled)  |  CPU Temp  | RAM: 666 MHz (DDR3-1333) - BCLK: 100
State: - Running...       |    59 C    | Timings: CAS 9-9-10-24 @ 64-bit Mode
Cores:  1 Active /  1 Total (Run: All) | Pass:       0        Errors:      0
------------------------------------------------------------------------------

I got sick of waiting so I rebooted again and it all came up fine.
I have attached a file with all the logs from these steps.

The reason I am concerned is that I had another one of my APU boxes running 1.3.6 just lock up for some reason and was also fixed with a reboot. I could not find any logs for that one and it may not be related.
So my questions are:

  1.  Is this just an unlucky flash problem or could there be something more sinister?
  2.  Why did it need to do a Memtest when it rebooted. Is this a BiOS thing?

Thanks all.

Regards
Michael Knill

[Astlinux-users] AstLinux Pre-Release: astlinux-1.3-4312-7810c3

[Lonnie A. <li...@lo...>]

Announcing Pre-Release Version: astlinux-1.3-4312-7810c3

** Special Request **
Please take a few minutes to test the new web interface Edit tab using CodeMirror.  Besides reporting any issues, we would like to hear suggestions for any tweaks, added modes (syntax), etc. .  If you don't have a spare test box, spin-up the Guest VM x86-64bit ISO found here:
https://www.astlinux-project.org/dev.html

The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.

-- OpenSSL, major version bump to 1.1.1c, the new LTS series.  The previous 1.0.2 LTS series is EOL at the end of 2019.
   Many packages needed version bumps or patches to be compatible with the new OpenSSL 1.1 API.
   Initial testing looks good, more testing is appreciated.

-- Web Interface Edit tab, add support for CodeMirror text editing.
   (Tip: Shift-Reload browser to get the updated CSS style sheet)
   Keyboard Actions: (after clicking text edit area)
   Note: Windows users, use Ctrl instead of Cmd
   Cmd-f -> Find
   Cmd-g -> Find Next
   Cmd-/ -> Toggle Comment
   Cmd-. -> Toggle Comment
   Tab   -> Toggle between "fullscreen" (full-window) mode and normal
   Esc   -> Return to normal, "fullscreen" (full-window) mode off
   More info: https://doc.astlinux-project.org/userdoc:tt_web_interface_edit_codemirror_key_map

-- Fossil, major version bump to 2.9, adds numerous enhancements to the look and feel of the web interface

-- WireGuard VPN, version bump to 0.0.20190702

-- Complete Pre-Release ChangeLog:
https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt

New Documentation Topics:
Edit tab w/CodeMirror Keyboard Mapping -
- https://doc.astlinux-project.org/userdoc:tt_web_interface_edit_codemirror_key_map

Updated Documentation Topics:
Web Interface Display Font -
- https://doc.astlinux-project.org/userdoc:tt_web_interface_font

The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ...

AstLinux Project -> Development
https://www.astlinux-project.org/dev.html

"Development" tab feature for desktop browsers:
Guest VM x86-64bit ISO: Download Pre-Release Guest VM Install ISO (Video Console)


AstLinux Team

Re: [Astlinux-users] Astlinux on AWS

[Michael K. <mic...@ip...>]

Cool. 
May still test with AWS but will certainly test out Linode when its there. Yay thanks for that!

Regards
Michael Knill

On 27/7/19, 10:29 am, "Lonnie Abelbeck" <li...@lo...> wrote:

    Hi Michael,
    
    Linode publicly announced April 30
    "Keep an eye out for more announcements on our upcoming India and Sydney data centers"
    
    Just recently Mumbai India went online.
    https://blog.linode.com/2019/07/17/linode-mumbai-data-center-now-open/
    
    Before that was Toronto
    https://blog.linode.com/2019/04/30/linode-toronto-data-center-now-available/
    
    So if their team can add Sydney at the same pace, that implies October-ish. (only a guess)
    
    Lonnie
    
    
    
    
    
    > On Jul 26, 2019, at 6:21 PM, Michael Knill <mic...@ip...> wrote:
    > 
    > Hi All
    > 
    > As I will be building an Astlinux based Softswitch for my customers, I am looking for a reliable hosting provider. Unfortunately there do not seem to be many here that will allow me to build with a custom ISO other than using a dedicated server on VMWare IaaS. Although this will be a good option, I am also looking at trialling Astlinux in AWS. PS I love Vultr but I don't think they will be good enough.
    > 
    > We will be doing this by importing a VMWare image to AWS. Can anyone see any gotchas? Has anyone done this before?
    > 
    > Regards
    > Michael Knill
    > 
    > On 22/8/18, 12:24 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
    > 
    >    Hi Michael,
    > 
    >    No I haven't, but it does look like you can import VMware images.
    > 
    >    I really like Linode for AstLinux in the cloud, but sadly there is no Linode locations in Australia (yet).
    > 
    >    If you wouldn't mind, hows does the latency compare for you:
    > 
    >    Linode - Asia Pacific (Tokyo)
    >    ping -q -c10 speedtest.tokyo2.linode.com
    > 
    >    Linode - Asia Pacific (Singapore)
    >    ping -q -c10 speedtest.singapore.linode.com
    > 
    >    AWS - Asia Pacific (Sydney)
    >    ping -q -c10 dynamodb.ap-southeast-2.amazonaws.com
    > 
    > 
    >    Lonnie
    > 
    > 
    >> On Aug 21, 2018, at 5:37 PM, Michael Knill <mic...@ip...> wrote:
    >> 
    >> Wow it looks hard to install Astlinux in EC2. You have to build it locally and import.
    >> Has anyone done this?
    >> 
    >> Regards
    >> Michael Knill
    > 
    > 
    > 
    > 
    >    ------------------------------------------------------------------------------
    >    Check out the vibrant tech community on one of the world's most
    >    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    >    _______________________________________________
    >    Astlinux-users mailing list
    >    Ast...@li...
    >    https://lists.sourceforge.net/lists/listinfo/astlinux-users
    > 
    >    Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
    > 
    > 
    > 
    > _______________________________________________
    > Astlinux-users mailing list
    > Ast...@li...
    > https://lists.sourceforge.net/lists/listinfo/astlinux-users
    > 
    > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
    
    
    
    _______________________________________________
    Astlinux-users mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-users
    
    Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Astlinux on AWS

[Lonnie A. <li...@lo...>]

Hi Michael,

Linode publicly announced April 30
"Keep an eye out for more announcements on our upcoming India and Sydney data centers"

Just recently Mumbai India went online.
https://blog.linode.com/2019/07/17/linode-mumbai-data-center-now-open/

Before that was Toronto
https://blog.linode.com/2019/04/30/linode-toronto-data-center-now-available/

So if their team can add Sydney at the same pace, that implies October-ish. (only a guess)

Lonnie





> On Jul 26, 2019, at 6:21 PM, Michael Knill <mic...@ip...> wrote:
> 
> Hi All
> 
> As I will be building an Astlinux based Softswitch for my customers, I am looking for a reliable hosting provider. Unfortunately there do not seem to be many here that will allow me to build with a custom ISO other than using a dedicated server on VMWare IaaS. Although this will be a good option, I am also looking at trialling Astlinux in AWS. PS I love Vultr but I don't think they will be good enough.
> 
> We will be doing this by importing a VMWare image to AWS. Can anyone see any gotchas? Has anyone done this before?
> 
> Regards
> Michael Knill
> 
> On 22/8/18, 12:24 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
> 
>    Hi Michael,
> 
>    No I haven't, but it does look like you can import VMware images.
> 
>    I really like Linode for AstLinux in the cloud, but sadly there is no Linode locations in Australia (yet).
> 
>    If you wouldn't mind, hows does the latency compare for you:
> 
>    Linode - Asia Pacific (Tokyo)
>    ping -q -c10 speedtest.tokyo2.linode.com
> 
>    Linode - Asia Pacific (Singapore)
>    ping -q -c10 speedtest.singapore.linode.com
> 
>    AWS - Asia Pacific (Sydney)
>    ping -q -c10 dynamodb.ap-southeast-2.amazonaws.com
> 
> 
>    Lonnie
> 
> 
>> On Aug 21, 2018, at 5:37 PM, Michael Knill <mic...@ip...> wrote:
>> 
>> Wow it looks hard to install Astlinux in EC2. You have to build it locally and import.
>> Has anyone done this?
>> 
>> Regards
>> Michael Knill
> 
> 
> 
> 
>    ------------------------------------------------------------------------------
>    Check out the vibrant tech community on one of the world's most
>    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>    _______________________________________________
>    Astlinux-users mailing list
>    Ast...@li...
>    https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
>    Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Astlinux on AWS

[Michael K. <mic...@ip...>]

Hi All

As I will be building an Astlinux based Softswitch for my customers, I am looking for a reliable hosting provider. Unfortunately there do not seem to be many here that will allow me to build with a custom ISO other than using a dedicated server on VMWare IaaS. Although this will be a good option, I am also looking at trialling Astlinux in AWS. PS I love Vultr but I don't think they will be good enough.

We will be doing this by importing a VMWare image to AWS. Can anyone see any gotchas? Has anyone done this before?

Regards
Michael Knill

On 22/8/18, 12:24 pm, "Lonnie Abelbeck" <li...@lo...> wrote:

    Hi Michael,
    
    No I haven't, but it does look like you can import VMware images.
    
    I really like Linode for AstLinux in the cloud, but sadly there is no Linode locations in Australia (yet).
    
    If you wouldn't mind, hows does the latency compare for you:
    
    Linode - Asia Pacific (Tokyo)
    ping -q -c10 speedtest.tokyo2.linode.com
    
    Linode - Asia Pacific (Singapore)
    ping -q -c10 speedtest.singapore.linode.com
    
    AWS - Asia Pacific (Sydney)
    ping -q -c10 dynamodb.ap-southeast-2.amazonaws.com
    
    
    Lonnie
    
    
    > On Aug 21, 2018, at 5:37 PM, Michael Knill <mic...@ip...> wrote:
    > 
    > Wow it looks hard to install Astlinux in EC2. You have to build it locally and import.
    > Has anyone done this?
    >  
    > Regards
    > Michael Knill
    
    
    
    
    ------------------------------------------------------------------------------
    Check out the vibrant tech community on one of the world's most
    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    _______________________________________________
    Astlinux-users mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-users
    
    Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
    

Re: [Astlinux-users] Cron jobs not running (solved)

[Lonnie A. <li...@lo...>]

David,

Do you still have your saved Basic Backup ?  If so a "tar tzvf backup.tar.gz" to see what the owner was.

Lonnie


> On Jul 26, 2019, at 2:21 PM, David Kerr <da...@ke...> wrote:
> 
> The file permissions were correctly preserved.  The file ownership was not.  I don't recall exactly when I did this in my setup process... likely very early.  I think I'll fire up a new VM with fresh AstLinux install and see if I can reproduce it.
> 
> Thanks
> David
> 
> On Fri, Jul 26, 2019 at 3:11 PM Lonnie Abelbeck <li...@lo...> wrote:
> David,
> 
> Great you figured it out, I have never seen that issue.
> 
> The "/usr/sbin/restore-basic-conf" (Basic Restore) script should preserve file permissions (uses tar) and via our web interface PHP has sufficient privileges to set root permissions.
> 
> As a test, I generated a basic config via the web interface, renamed /mnt/kd/crontabs/root and then did a "Restore Basic" via the System tab, resulting in:
> --
> # ls -l /mnt/kd/crontabs/
> total 4
> -rw-------    1 root     root           358 Jul 26 10:45 root
> --
> The original (backup) file permissions were preserved.
> 
> User 1000 is not a standard user, but probably a manual "adduser".
> 
> 
> > I wonder if there are any other files created by restore basic configuration that are sensitive to ownership?
> 
> Prosody (XMPP) is sensitive to file ownership in /mnt/kd/ .  A few others have 0600 permissions.
> 
> Lonnie
> 
> 
> 
> > On Jul 26, 2019, at 1:53 PM, David Kerr <da...@ke...> wrote:
> > 
> > 
> > 
> > Lonnie,
> >   Found the problem.  The file /mnt/kd/crontabs/root had owner of "1000" in group "root"
> > It appears that crond is sensitive to the file owner, so I did a chown to change the owner to "root" and things started to work.
> > 
> > Looking at my /mnt/kd, I found dozens of files that have 1000 as the owner.  I am guessing that when I did a restore basic configuration from the web interface all the files were created by user 1000.
> > 
> > I wonder if there are any other files created by restore basic configuration that are sensitive to ownership?
> > 
> > David
> > 
> > On Fri, Jul 26, 2019 at 11:47 AM Lonnie Abelbeck <li...@lo...> wrote:
> > Hmmm...
> > 
> > Using either "crontab -e" or the Edit tab and "Reload Cron for root" add this line:
> > --
> > * * * * * /bin/date >/tmp/foo
> > --
> > If you are not seeing it /var/log/messages see if /tmp/foo exists.
> > 
> > If /tmp/foo is created then it may be some logging issue.
> > 
> > This works for me.  I can't image what you have incorrect.
> > 
> > Lonnie
> > 
> > 
> > 
> > > On Jul 26, 2019, at 10:30 AM, David Kerr <da...@ke...> wrote:
> > > 
> > > Hi Lonnie.
> > >   Yes, crontab -l shows what I expect...
> > > 
> > > pbx ~ # crontab -l
> > > ##
> > > ## logrotate - Do not remove, comment-out to disable
> > > 00 04 * * * /usr/sbin/logrotate /etc/logrotate.conf >/dev/null 2>&1
> > > 
> > > ##
> > > ## Fossil daily auto-commit - Do not remove, un-comment to enable
> > > 55 23 * * * /usr/bin/fossil-commit >/dev/null 2>&1
> > > <cut off the rest>
> > > 
> > > and yes /ver/spool/cron/crontabs is symlinked over to /mnt/kd.  And the crond process is running...
> > > 
> > > Jul 26 09:55:17 pbx cron.info crond[1135]: crond (busybox 1.30.1) started, log level 8
> > > But nothing is executing overnight !
> > > 
> > > Thanks
> > > David
> > > 
> > > 
> > > 
> > > On Fri, Jul 26, 2019 at 10:39 AM Lonnie Abelbeck <li...@lo...> wrote:
> > > Hi David,
> > > 
> > > Busybox crond uses "/var/spool/cron/crontabs"
> > > --
> > > # ls -l /var/spool/cron/crontabs 
> > > lrwxrwxrwx    1 root     root            16 Jul 23 17:42 /var/spool/cron/crontabs -> /mnt/kd/crontabs
> > > --
> > > which is (should be) symlinked to "/mnt/kd/crontabs"
> > > --
> > > # ls -l /mnt/kd/crontabs
> > > total 4
> > > -rw-------    1 root     root           358 Oct 29  2017 root
> > > --
> > > 
> > > Also see if "crontab -l" shows what you expect.
> > > 
> > > BTW, Thanks, I did not know "/etc/cron.d" was being installed, we should remove that.
> > > 
> > > Lonnie
> > > 
> > > 
> > > 
> > > > On Jul 26, 2019, at 9:01 AM, David Kerr <da...@ke...> wrote:
> > > > 
> > > > I just noticed since moving to a new system that my cron jobs are not running.  The configuration of the new system was established by doing a "restore basic configuration" from the system tab.  I cannot figure out why it is not working.
> > > > 
> > > > crond is running (ps | grep "crond") and startup is logged in syslog.
> > > > /var/spool/cron/crontabs exists, is link to...
> > > > /mnt/kd/crontabs
> > > > inside that is "root" which is file placed there by the restore configuration.  It has permissions 600
> > > > /etc/cron.d also exists
> > > > inside that is "e2scrub_all" which has permissions 644
> > > > 
> > > > I tried changing permissions on "root" to 644 but that made no difference.
> > > > 
> > > > What am I missing?
> > > > 
> > > > Thanks
> > > > David
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Astlinux-users mailing list
> > > > Ast...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > > > 
> > > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Astlinux-users mailing list
> > > Ast...@li...
> > > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > > 
> > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> > > _______________________________________________
> > > Astlinux-users mailing list
> > > Ast...@li...
> > > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > > 
> > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> > 
> > 
> > 
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > 
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > 
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Cron jobs not running (solved)

[David K. <da...@ke...>]

The file permissions were correctly preserved.  The file ownership was
not.  I don't recall exactly when I did this in my setup process... likely
very early.  I think I'll fire up a new VM with fresh AstLinux install and
see if I can reproduce it.

Thanks
David

On Fri, Jul 26, 2019 at 3:11 PM Lonnie Abelbeck <li...@lo...>
wrote:

> David,
>
> Great you figured it out, I have never seen that issue.
>
> The "/usr/sbin/restore-basic-conf" (Basic Restore) script should preserve
> file permissions (uses tar) and via our web interface PHP has sufficient
> privileges to set root permissions.
>
> As a test, I generated a basic config via the web interface, renamed
> /mnt/kd/crontabs/root and then did a "Restore Basic" via the System tab,
> resulting in:
> --
> # ls -l /mnt/kd/crontabs/
> total 4
> -rw-------    1 root     root           358 Jul 26 10:45 root
> --
> The original (backup) file permissions were preserved.
>
> User 1000 is not a standard user, but probably a manual "adduser".
>
>
> > I wonder if there are any other files created by restore basic
> configuration that are sensitive to ownership?
>
> Prosody (XMPP) is sensitive to file ownership in /mnt/kd/ .  A few others
> have 0600 permissions.
>
> Lonnie
>
>
>
> > On Jul 26, 2019, at 1:53 PM, David Kerr <da...@ke...> wrote:
> >
> >
> >
> > Lonnie,
> >   Found the problem.  The file /mnt/kd/crontabs/root had owner of "1000"
> in group "root"
> > It appears that crond is sensitive to the file owner, so I did a chown
> to change the owner to "root" and things started to work.
> >
> > Looking at my /mnt/kd, I found dozens of files that have 1000 as the
> owner.  I am guessing that when I did a restore basic configuration from
> the web interface all the files were created by user 1000.
> >
> > I wonder if there are any other files created by restore basic
> configuration that are sensitive to ownership?
> >
> > David
> >
> > On Fri, Jul 26, 2019 at 11:47 AM Lonnie Abelbeck <
> li...@lo...> wrote:
> > Hmmm...
> >
> > Using either "crontab -e" or the Edit tab and "Reload Cron for root" add
> this line:
> > --
> > * * * * * /bin/date >/tmp/foo
> > --
> > If you are not seeing it /var/log/messages see if /tmp/foo exists.
> >
> > If /tmp/foo is created then it may be some logging issue.
> >
> > This works for me.  I can't image what you have incorrect.
> >
> > Lonnie
> >
> >
> >
> > > On Jul 26, 2019, at 10:30 AM, David Kerr <da...@ke...> wrote:
> > >
> > > Hi Lonnie.
> > >   Yes, crontab -l shows what I expect...
> > >
> > > pbx ~ # crontab -l
> > > ##
> > > ## logrotate - Do not remove, comment-out to disable
> > > 00 04 * * * /usr/sbin/logrotate /etc/logrotate.conf >/dev/null 2>&1
> > >
> > > ##
> > > ## Fossil daily auto-commit - Do not remove, un-comment to enable
> > > 55 23 * * * /usr/bin/fossil-commit >/dev/null 2>&1
> > > <cut off the rest>
> > >
> > > and yes /ver/spool/cron/crontabs is symlinked over to /mnt/kd.  And
> the crond process is running...
> > >
> > > Jul 26 09:55:17 pbx cron.info crond[1135]: crond (busybox 1.30.1)
> started, log level 8
> > > But nothing is executing overnight !
> > >
> > > Thanks
> > > David
> > >
> > >
> > >
> > > On Fri, Jul 26, 2019 at 10:39 AM Lonnie Abelbeck <
> li...@lo...> wrote:
> > > Hi David,
> > >
> > > Busybox crond uses "/var/spool/cron/crontabs"
> > > --
> > > # ls -l /var/spool/cron/crontabs
> > > lrwxrwxrwx    1 root     root            16 Jul 23 17:42
> /var/spool/cron/crontabs -> /mnt/kd/crontabs
> > > --
> > > which is (should be) symlinked to "/mnt/kd/crontabs"
> > > --
> > > # ls -l /mnt/kd/crontabs
> > > total 4
> > > -rw-------    1 root     root           358 Oct 29  2017 root
> > > --
> > >
> > > Also see if "crontab -l" shows what you expect.
> > >
> > > BTW, Thanks, I did not know "/etc/cron.d" was being installed, we
> should remove that.
> > >
> > > Lonnie
> > >
> > >
> > >
> > > > On Jul 26, 2019, at 9:01 AM, David Kerr <da...@ke...> wrote:
> > > >
> > > > I just noticed since moving to a new system that my cron jobs are
> not running.  The configuration of the new system was established by doing
> a "restore basic configuration" from the system tab.  I cannot figure out
> why it is not working.
> > > >
> > > > crond is running (ps | grep "crond") and startup is logged in syslog.
> > > > /var/spool/cron/crontabs exists, is link to...
> > > > /mnt/kd/crontabs
> > > > inside that is "root" which is file placed there by the restore
> configuration.  It has permissions 600
> > > > /etc/cron.d also exists
> > > > inside that is "e2scrub_all" which has permissions 644
> > > >
> > > > I tried changing permissions on "root" to 644 but that made no
> difference.
> > > >
> > > > What am I missing?
> > > >
> > > > Thanks
> > > > David
> > > >
> > > >
> > > > _______________________________________________
> > > > Astlinux-users mailing list
> > > > Ast...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > > >
> > > > Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
> > >
> > >
> > >
> > > _______________________________________________
> > > Astlinux-users mailing list
> > > Ast...@li...
> > > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > >
> > > Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
> > > _______________________________________________
> > > Astlinux-users mailing list
> > > Ast...@li...
> > > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > >
> > > Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
> >
> >
> >
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>

Re: [Astlinux-users] Cron jobs not running (solved)

[Lonnie A. <li...@lo...>]

David,

Great you figured it out, I have never seen that issue.

The "/usr/sbin/restore-basic-conf" (Basic Restore) script should preserve file permissions (uses tar) and via our web interface PHP has sufficient privileges to set root permissions.

As a test, I generated a basic config via the web interface, renamed /mnt/kd/crontabs/root and then did a "Restore Basic" via the System tab, resulting in:
--
# ls -l /mnt/kd/crontabs/
total 4
-rw-------    1 root     root           358 Jul 26 10:45 root
--
The original (backup) file permissions were preserved.

User 1000 is not a standard user, but probably a manual "adduser".


> I wonder if there are any other files created by restore basic configuration that are sensitive to ownership?

Prosody (XMPP) is sensitive to file ownership in /mnt/kd/ .  A few others have 0600 permissions.

Lonnie



> On Jul 26, 2019, at 1:53 PM, David Kerr <da...@ke...> wrote:
> 
> 
> 
> Lonnie,
>   Found the problem.  The file /mnt/kd/crontabs/root had owner of "1000" in group "root"
> It appears that crond is sensitive to the file owner, so I did a chown to change the owner to "root" and things started to work.
> 
> Looking at my /mnt/kd, I found dozens of files that have 1000 as the owner.  I am guessing that when I did a restore basic configuration from the web interface all the files were created by user 1000.
> 
> I wonder if there are any other files created by restore basic configuration that are sensitive to ownership?
> 
> David
> 
> On Fri, Jul 26, 2019 at 11:47 AM Lonnie Abelbeck <li...@lo...> wrote:
> Hmmm...
> 
> Using either "crontab -e" or the Edit tab and "Reload Cron for root" add this line:
> --
> * * * * * /bin/date >/tmp/foo
> --
> If you are not seeing it /var/log/messages see if /tmp/foo exists.
> 
> If /tmp/foo is created then it may be some logging issue.
> 
> This works for me.  I can't image what you have incorrect.
> 
> Lonnie
> 
> 
> 
> > On Jul 26, 2019, at 10:30 AM, David Kerr <da...@ke...> wrote:
> > 
> > Hi Lonnie.
> >   Yes, crontab -l shows what I expect...
> > 
> > pbx ~ # crontab -l
> > ##
> > ## logrotate - Do not remove, comment-out to disable
> > 00 04 * * * /usr/sbin/logrotate /etc/logrotate.conf >/dev/null 2>&1
> > 
> > ##
> > ## Fossil daily auto-commit - Do not remove, un-comment to enable
> > 55 23 * * * /usr/bin/fossil-commit >/dev/null 2>&1
> > <cut off the rest>
> > 
> > and yes /ver/spool/cron/crontabs is symlinked over to /mnt/kd.  And the crond process is running...
> > 
> > Jul 26 09:55:17 pbx cron.info crond[1135]: crond (busybox 1.30.1) started, log level 8
> > But nothing is executing overnight !
> > 
> > Thanks
> > David
> > 
> > 
> > 
> > On Fri, Jul 26, 2019 at 10:39 AM Lonnie Abelbeck <li...@lo...> wrote:
> > Hi David,
> > 
> > Busybox crond uses "/var/spool/cron/crontabs"
> > --
> > # ls -l /var/spool/cron/crontabs 
> > lrwxrwxrwx    1 root     root            16 Jul 23 17:42 /var/spool/cron/crontabs -> /mnt/kd/crontabs
> > --
> > which is (should be) symlinked to "/mnt/kd/crontabs"
> > --
> > # ls -l /mnt/kd/crontabs
> > total 4
> > -rw-------    1 root     root           358 Oct 29  2017 root
> > --
> > 
> > Also see if "crontab -l" shows what you expect.
> > 
> > BTW, Thanks, I did not know "/etc/cron.d" was being installed, we should remove that.
> > 
> > Lonnie
> > 
> > 
> > 
> > > On Jul 26, 2019, at 9:01 AM, David Kerr <da...@ke...> wrote:
> > > 
> > > I just noticed since moving to a new system that my cron jobs are not running.  The configuration of the new system was established by doing a "restore basic configuration" from the system tab.  I cannot figure out why it is not working.
> > > 
> > > crond is running (ps | grep "crond") and startup is logged in syslog.
> > > /var/spool/cron/crontabs exists, is link to...
> > > /mnt/kd/crontabs
> > > inside that is "root" which is file placed there by the restore configuration.  It has permissions 600
> > > /etc/cron.d also exists
> > > inside that is "e2scrub_all" which has permissions 644
> > > 
> > > I tried changing permissions on "root" to 644 but that made no difference.
> > > 
> > > What am I missing?
> > > 
> > > Thanks
> > > David
> > > 
> > > 
> > > _______________________________________________
> > > Astlinux-users mailing list
> > > Ast...@li...
> > > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > > 
> > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> > 
> > 
> > 
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > 
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > 
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Cron jobs not running (solved)

[David K. <da...@ke...>]

Lonnie,
  Found the problem.  The file /mnt/kd/crontabs/root had owner of "1000" in
group "root"
It appears that crond is sensitive to the file owner, so I did a chown to
change the owner to "root" and things started to work.

Looking at my /mnt/kd, I found dozens of files that have 1000 as the
owner.  I am guessing that when I did a restore basic configuration from
the web interface all the files were created by user 1000.

I wonder if there are any other files created by restore basic
configuration that are sensitive to ownership?

David

On Fri, Jul 26, 2019 at 11:47 AM Lonnie Abelbeck <li...@lo...>
wrote:

> Hmmm...
>
> Using either "crontab -e" or the Edit tab and "Reload Cron for root" add
> this line:
> --
> * * * * * /bin/date >/tmp/foo
> --
> If you are not seeing it /var/log/messages see if /tmp/foo exists.
>
> If /tmp/foo is created then it may be some logging issue.
>
> This works for me.  I can't image what you have incorrect.
>
> Lonnie
>
>
>
> > On Jul 26, 2019, at 10:30 AM, David Kerr <da...@ke...> wrote:
> >
> > Hi Lonnie.
> >   Yes, crontab -l shows what I expect...
> >
> > pbx ~ # crontab -l
> > ##
> > ## logrotate - Do not remove, comment-out to disable
> > 00 04 * * * /usr/sbin/logrotate /etc/logrotate.conf >/dev/null 2>&1
> >
> > ##
> > ## Fossil daily auto-commit - Do not remove, un-comment to enable
> > 55 23 * * * /usr/bin/fossil-commit >/dev/null 2>&1
> > <cut off the rest>
> >
> > and yes /ver/spool/cron/crontabs is symlinked over to /mnt/kd.  And the
> crond process is running...
> >
> > Jul 26 09:55:17 pbx cron.info crond[1135]: crond (busybox 1.30.1)
> started, log level 8
> > But nothing is executing overnight !
> >
> > Thanks
> > David
> >
> >
> >
> > On Fri, Jul 26, 2019 at 10:39 AM Lonnie Abelbeck <
> li...@lo...> wrote:
> > Hi David,
> >
> > Busybox crond uses "/var/spool/cron/crontabs"
> > --
> > # ls -l /var/spool/cron/crontabs
> > lrwxrwxrwx    1 root     root            16 Jul 23 17:42
> /var/spool/cron/crontabs -> /mnt/kd/crontabs
> > --
> > which is (should be) symlinked to "/mnt/kd/crontabs"
> > --
> > # ls -l /mnt/kd/crontabs
> > total 4
> > -rw-------    1 root     root           358 Oct 29  2017 root
> > --
> >
> > Also see if "crontab -l" shows what you expect.
> >
> > BTW, Thanks, I did not know "/etc/cron.d" was being installed, we should
> remove that.
> >
> > Lonnie
> >
> >
> >
> > > On Jul 26, 2019, at 9:01 AM, David Kerr <da...@ke...> wrote:
> > >
> > > I just noticed since moving to a new system that my cron jobs are not
> running.  The configuration of the new system was established by doing a
> "restore basic configuration" from the system tab.  I cannot figure out why
> it is not working.
> > >
> > > crond is running (ps | grep "crond") and startup is logged in syslog.
> > > /var/spool/cron/crontabs exists, is link to...
> > > /mnt/kd/crontabs
> > > inside that is "root" which is file placed there by the restore
> configuration.  It has permissions 600
> > > /etc/cron.d also exists
> > > inside that is "e2scrub_all" which has permissions 644
> > >
> > > I tried changing permissions on "root" to 644 but that made no
> difference.
> > >
> > > What am I missing?
> > >
> > > Thanks
> > > David
> > >
> > >
> > > _______________________________________________
> > > Astlinux-users mailing list
> > > Ast...@li...
> > > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > >
> > > Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
> >
> >
> >
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> >
> > Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>

Re: [Astlinux-users] Cron jobs not running

[Lonnie A. <li...@lo...>]

Hmmm...

Using either "crontab -e" or the Edit tab and "Reload Cron for root" add this line:
--
* * * * * /bin/date >/tmp/foo
--
If you are not seeing it /var/log/messages see if /tmp/foo exists.

If /tmp/foo is created then it may be some logging issue.

This works for me.  I can't image what you have incorrect.

Lonnie



> On Jul 26, 2019, at 10:30 AM, David Kerr <da...@ke...> wrote:
> 
> Hi Lonnie.
>   Yes, crontab -l shows what I expect...
> 
> pbx ~ # crontab -l
> ##
> ## logrotate - Do not remove, comment-out to disable
> 00 04 * * * /usr/sbin/logrotate /etc/logrotate.conf >/dev/null 2>&1
> 
> ##
> ## Fossil daily auto-commit - Do not remove, un-comment to enable
> 55 23 * * * /usr/bin/fossil-commit >/dev/null 2>&1
> <cut off the rest>
> 
> and yes /ver/spool/cron/crontabs is symlinked over to /mnt/kd.  And the crond process is running...
> 
> Jul 26 09:55:17 pbx cron.info crond[1135]: crond (busybox 1.30.1) started, log level 8
> But nothing is executing overnight !
> 
> Thanks
> David
> 
> 
> 
> On Fri, Jul 26, 2019 at 10:39 AM Lonnie Abelbeck <li...@lo...> wrote:
> Hi David,
> 
> Busybox crond uses "/var/spool/cron/crontabs"
> --
> # ls -l /var/spool/cron/crontabs 
> lrwxrwxrwx    1 root     root            16 Jul 23 17:42 /var/spool/cron/crontabs -> /mnt/kd/crontabs
> --
> which is (should be) symlinked to "/mnt/kd/crontabs"
> --
> # ls -l /mnt/kd/crontabs
> total 4
> -rw-------    1 root     root           358 Oct 29  2017 root
> --
> 
> Also see if "crontab -l" shows what you expect.
> 
> BTW, Thanks, I did not know "/etc/cron.d" was being installed, we should remove that.
> 
> Lonnie
> 
> 
> 
> > On Jul 26, 2019, at 9:01 AM, David Kerr <da...@ke...> wrote:
> > 
> > I just noticed since moving to a new system that my cron jobs are not running.  The configuration of the new system was established by doing a "restore basic configuration" from the system tab.  I cannot figure out why it is not working.
> > 
> > crond is running (ps | grep "crond") and startup is logged in syslog.
> > /var/spool/cron/crontabs exists, is link to...
> > /mnt/kd/crontabs
> > inside that is "root" which is file placed there by the restore configuration.  It has permissions 600
> > /etc/cron.d also exists
> > inside that is "e2scrub_all" which has permissions 644
> > 
> > I tried changing permissions on "root" to 644 but that made no difference.
> > 
> > What am I missing?
> > 
> > Thanks
> > David
> > 
> > 
> > _______________________________________________
> > Astlinux-users mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-users
> > 
> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> 
> 
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....