Re: fail to powerdown from installed system

2023-09-27 Thread Dimitrios Moustos 

Please try -current first.

Indeed, a bad omission.
More editing quality control next time.

The amd64 machine fails to power down while running:
7.2
7.3
current (as of 2023-09-20)

Today (2023-09-27) I installed latest snapshot on a usb stick, same issue.
The snapshot: https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/

The install bsd.rd successfuly rebooted after pressing R+Enter (as expected).
The booted up system stalled after either reboot or halt -p.


It might be noted that there are a few not configured devices:
dot ~$ dmesg|grep "not configured"
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"AMD 17h/6xh IOMMU" rev 0x00 at pci0 dev 0 function 2 not configured
vendor "AMD", unknown product 0x1485 (class instrumentation unknown subclass 
0x00, rev 0x00) at pci5 dev 0 function 0 not configured
efifb at mainbus0 not configured

fail to powerdown from installed system

2023-09-26 Thread Dimitrios Moustos 

Hello,

The system whose dmesg is attached fails to powerdown or reboot.
I am not sure if it is a bug, a misconfiguration or a missing or incomplete 
driver.
After halt -p from an installed system the system hangs after:
syncing disks... done

and in case of a reboot:
syncing disks... done
rebooting...

(incl the linebreak after rebooting...)
But the system just hangs, making the machine unusable as a server.

When this happens:
Power down  halt -p or reboot this particular system.
Tested multiple disks: sata ssd, nvme
Multiple installations: gpt, mbr, legacy boot, uefi boot, autopartition, with 
swap, without swap.
I particularly tested with and without the Intel Optane nvme, no difference 
with or without
Single user mode also hangs at powerdown

When can the system power down:
Other systems running the same ssd can powerdown or reboot. (current dmesg is 
running from nvme)
bsd.rd can powerdown and reboot successfully running on this system
In boot if I do a machine powerdown the machine powers down successfully.
Of course, I tested a bunch of linux distributions and windows and all powered 
down.

I believe the problem appeared arround openbsd 7.2, or 7.1. I am not sure.
Knowing exactly when the problem appeared might help locate the problem.
In this case I will install some older versions and report back.

Any info is appreciated.
If I should report back with more info I will be happy to.

Thank you all for keeping OpenBSD going,
Dimitrios
OpenBSD 7.3 (GENERIC.MP) #3: Tue Jul 25 08:20:26 MDT 2023

r...@syspatch-73-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16462909440 (15700MB)
avail mem = 15944552448 (15205MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xe8d60 (48 entries)
bios0: vendor American Megatrends International, LLC. version "F37f" date 
08/09/2023
bios0: Gigabyte Technology Co., Ltd. X570 AORUS PRO
efi0 at bios0: UEFI 2.7
efi0: American Megatrends rev 0x50011
acpi0 at bios0: ACPI 6.2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT IVRS SSDT SSDT SSDT FIDT MCFG HPET SSDT FPDT TPM2 
SSDT CRAT CDIT SSDT SSDT SSDT WSMT APIC SSDT SSDT
acpi0: wakeup devices GPP0(S4) GPP2(S4) GPP3(S4) GPP4(S4) GPP5(S4) GP17(S4) 
XHC0(S4) XHC1(S4) GP18(S4) BXBR(S4)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimcfg0 at acpi0
acpimcfg0: addr 0xf000, bus 0-127
acpihpet0 at acpi0: 14318180 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Ryzen 5 PRO 5650G with Radeon Graphics, 3900.01 MHz, 19-50-00
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,WAITPKG,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 
8-way L2 cache, 16MB 64b/line 16-way L3 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 100MHz
cpu0: mwait min=64, max=64, C-substates=1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: AMD Ryzen 5 PRO 5650G with Radeon Graphics, 3900.00 MHz, 19-50-00
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 
8-way L2 cache, 16MB 64b/line 16-way L3 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: AMD Ryzen 5 PRO 5650G with Radeon Graphics, 3900.00 MHz, 19-50-00
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 
8-way L2 cache, 16MB 64b/line 16-way L3 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6

renewing let's encrypt renewal for multihost, multi-domain solved

2022-10-03 Thread Dimitrios Moustos 

Hello,

I have three domains, ex. example.com, company.com, and masterhost.com,
with example.com and company.com being served by both master and slave http 
hosts.

All three domain names are under alternative names for acme-client.

The problem I have been having while renewing Let's Encrypt certificates is
that the masater host would issue the acme-client command,
and Let's Encrypt would also contact the slave host
to check if it has the response to the challenge, obviously it would not.

I have solved this by including the following on the slave host:

location "/.well-known/acme-challenge/*" {
block return 301 "https://masterhost.com/$DOCUMENT_URI;
}

With this in place I sucessfully renewed my certificate without needing to 
resort to DNS-01 or to temporarily removing the slave host from dns records 
while renewing.


Dimitrios

rDNS checks in spamd

2019-12-03 Thread Dimitrios Moustos 
Hello,

I notice quite a few hosts without rDNS/FCrDNS getting whitelisted by
spamd.

I reject hosts with no rDNS using the following in my crontab:

(spamdb|for i in `awk -F'|' '/GREY/{print $2}'`; do if ! host $i >/dev/null; 
then spamdb -dG $i; fi; done)

It works, but it does not feel like it is the best way to do it.

OpenSMTPD rejects the hosts without RCrDNS using a filter anyways, but
it feels better to know that smtpd is not talking directly to these
likely suspicious hosts.

Does it make sense to add a rDNS check option to spamd?
(if not a full FCrDNS check)
If so then I could work on it.

Thanks, Dimitrios

Re: syspatch -c (amd64) ftp: connect: Permission denied

2019-11-14 Thread Dimitrios Moustos 
Hello Strahil,

I get this very often when pf does not allow traffic out.
First check that pf allows traffic out.

Hope it helps, Dimitrios

On Wed, Nov 13, 2019 at 10:51:45PM +, Strahil Nikolov wrote:
> Hello Community,
> 
> it seems that syspatch and pkg_add are having an issue with 'ftp: connect: 
> Permission denied'.
> System is 6.5 and access via ftp (based on my automatic syspatch script) has 
> seized on 03 Nov 2019.
> /etc/installurl is pointing to https://cdn.openbsd.org/pub/OpenBSD/ 
> 
> Is syspatch working for you ?
> 
> 
> Thanks in advance.
> 
> Best Regards,
> Strahil Nikolov
>

filesystem mount sync and async

2012-06-11 Thread Dimitrios Moustos 
Hello,
I have not found any information in the man page or otherwise that conflicts 
with the bellow, it just does not seem like the following should be possible:

# grep home /etc/fstab
424dc014a22db950.f /home ffs ro,nodev,nosuid,noatime
# mount|grep home
/dev/sd0f on /home type ffs (local, noatime, nodev, nosuid, read-only)
# mount -uwo async /home
# mount|grep home
/dev/sd0f on /home type ffs (asynchronous, local, noatime, nodev, nosuid)
# mount -uro sync /home
# mount|grep /home
/dev/sd0f on /home type ffs (asynchronous, local, noatime, nodev, nosuid, 
read-only, synchronous)


I am however not familiar with the intricacies of filesystems, which probably 
makes me wrong.
At least posting this will make my curiosity go away.