python3 script not running as root
Hi all, I have a python script to get some traffic stats from my machines and it is running without problems except for a new installed OpenBSD 6.4 machine. There I get following error: env: python3: No such file or directory This only happens when the cronjob is running when I run it from terminal with doas it works. That is kinda odd sice both root and my user have python3 and env in there $PATH at least the path to the executable. some hints would be appreciated. regards -- Markus Rosjatfon: +49 351 8107224mail: ros...@ghweb.de G+H Webservice GbR Gorzolla, Herrmann Königsbrücker Str. 70, 01099 Dresden http://www.ghweb.de fon: +49 351 8107220 fax: +49 351 8107227 Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before you print it, think about your responsibility and commitment to the ENVIRONMENT
Re: File sets on internet exposed server
On 2018-11-14, Aham Brahmasmi wrote: > Hello misc, > > 1) For an internet exposed server, would it be ok to not install any > i) compiler collection > ii) games > iii) X related > file sets? > Set name(s) = -comp* -game* -x* > > 2) Would ssh login be affected by lack of X related file sets on the > server? In other words, is ssh one of the "programs that manipulate > text or graphics" in the following paragraph? > > From https://www.openbsd.org/faq/faq4.html#FilesNeeded, > " > > New users are recommended to install all of them. > Some libraries from xbaseXX.tgz, like freetype or fontconfig, can be > used outside of X by programs that manipulate text or graphics. Such > programs will usually need fonts, either from xfontXX.tgz or font > packages. For the sake of simplicity, the developers decided against > maintaining a minimal xbaseXX.tgz set that would allow most non-X ports > to run. The xservXX.tgz set is rarely needed if you don't intend to run > X. > " > > The motivation for these questions is the recent X hole. xserv can probably be skipped in this case (and contains the program which had the recent problem). Some libraries in xbase are fairly widely used by packages. There are no setuid binaries in that set but there are two setgid (xlock is setgid auth, in order to run bsdauth programs, and xterm is setgid utmp, in order to update /var/run/utmp). If you are concerned by that you could mount /usr/X11R6 with the "nosuid" flag. If you aren't using those packages which use libraries from xbase, you *could* skip installing it, but make a note of it so that if you later run pkg_add and get weird errors about missing libraries, you know what you've done.
Re: File sets on internet exposed server
Skipping X and games is usually safe. The compilers might be a bad idea unless you're only installing software from ports. Sent from phone. On Wed, Nov 14, 2018 at 11:48 AM -0600, "Aham Brahmasmi" wrote: Hello misc, 1) For an internet exposed server, would it be ok to not install any i) compiler collection ii) games iii) X related file sets? Set name(s) = -comp* -game* -x* 2) Would ssh login be affected by lack of X related file sets on the server? In other words, is ssh one of the "programs that manipulate text or graphics" in the following paragraph? >From https://www.openbsd.org/faq/faq4.html#FilesNeeded, " New users are recommended to install all of them. Some libraries from xbaseXX.tgz, like freetype or fontconfig, can be used outside of X by programs that manipulate text or graphics. Such programs will usually need fonts, either from xfontXX.tgz or font packages. For the sake of simplicity, the developers decided against maintaining a minimal xbaseXX.tgz set that would allow most non-X ports to run. The xservXX.tgz set is rarely needed if you don't intend to run X. " The motivation for these questions is the recent X hole. Thanks. Regards, ab -|-|-|-|-|-|-|--
OpenBSD 6.2 - 6.4 crash on ASRock Q1900 ITX boards
Is there anything I can do to help possibly solve this problem? I'm running current on an ASrock J3355M http://daemonforums.org/showpost.php?p=63678=103 Baytrail motherboards have aggressive C-state power saving issues even in linux. https://wiki.archlinux.org/index.php/Intel_graphics#Baytrail_complete_freeze I disabled all c-states in the bios although C1 will probably be OK. Crashes/Lockups went away. -- J. Scott Heppler
File sets on internet exposed server
Hello misc, 1) For an internet exposed server, would it be ok to not install any i) compiler collection ii) games iii) X related file sets? Set name(s) = -comp* -game* -x* 2) Would ssh login be affected by lack of X related file sets on the server? In other words, is ssh one of the "programs that manipulate text or graphics" in the following paragraph? >From https://www.openbsd.org/faq/faq4.html#FilesNeeded, " New users are recommended to install all of them. Some libraries from xbaseXX.tgz, like freetype or fontconfig, can be used outside of X by programs that manipulate text or graphics. Such programs will usually need fonts, either from xfontXX.tgz or font packages. For the sake of simplicity, the developers decided against maintaining a minimal xbaseXX.tgz set that would allow most non-X ports to run. The xservXX.tgz set is rarely needed if you don't intend to run X. " The motivation for these questions is the recent X hole. Thanks. Regards, ab -|-|-|-|-|-|-|--
OpenBSD 6.2 - 6.4 crash on ASRock Q1900 ITX boards
Hi,
I have a couple of Q1900DC-ITX boards:
http://www.asrock.com/MB/Intel/Q1900DC-ITX/index.de.asp I also have a couple of
Q1900M versions of the same board.
On the ITX version OpenBSD (tested from 6.2 - 6.4) crashes upon reboot, but not
upon a cold boot, with the following:
NMI ... going to debugger
Stopped atacpicpu_idle+0x22d: nop
ddb{0}>
Is there anything I can do to help possibly solve this problem?
I also get these "annoying" ehci_sync_hc: tsleep() = 35 messages, as seen in
dmesg, on all boards during boot, which makes the boot process halt for 35
seconds. What is causing this?
Thanks in advance.
Kindest regards
dmesg:
OpenBSD 6.4 (GENERIC.MP) #364: Thu Oct 11 13:30:23 MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 1818173440 (1733MB)
avail mem = 1753853952 (1672MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebd40 (19 entries)
bios0: vendor American Megatrends Inc. version "P1.70" date 03/01/2018
bios0: ASRock Q1900DC-ITX
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG LPIT AAFT SSDT SSDT SSDT UEFI
acpi0: wakeup devices XHC1(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PWRB(S0)
BRCM(S0)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.45 MHz, 06-37-08
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 83MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 1999.99 MHz, 06-37-08
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 1999.99 MHz, 06-37-08
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 1999.99 MHz, 06-37-08
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN
cpu3: 1MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 87 pins
acpimadt0: bogus nmi for apid 0
acpimadt0: bogus nmi for apid 2
acpimadt0: bogus nmi for apid 4
acpimadt0: bogus nmi for apid 6
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (RP03)
acpiprt4 at acpi0: bus 4 (RP04)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1
mwait.1), PSS
acpicpu1 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1
mwait.1), PSS
acpicpu2 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1
mwait.1), PSS
acpicpu3 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1
mwait.1), PSS
acpipwrres0 at acpi0: PLPE
acpipwrres1 at acpi0: PLPE
acpipwrres2 at acpi0: USBC, resource for EHC1, OTG1
acpipwrres3 at acpi0: CLK0, resource for CAM1
acpipwrres4 at acpi0: CLK1, resource for CAM0, CAM2
acpipwrres5 at acpi0: FN00, resource for FAN0
acpitz0 at acpi0: critical temperature is 90 degC
"INT3396" at acpi0 not configured
acpicmos0 at acpi0
"DMA0F28" at acpi0 not configured
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
"BCM2E1A" at acpi0 not configured
"BCM4752" at acpi0 not configured
"INTCF0B" at acpi0 not configured
"INTCF1A" at acpi0 not configured
"INTCF1C" at acpi0 not configured
"SMO91D0" at acpi0 not
ssh-keygen(1) manpage
Hello misc, For the ssh-keygen manpage, https://man.openbsd.org/ssh-keygen.1: 1) We may possibly be missing "-a rounds" for the first incantation ssh-keygen [-q ] [-b bits ] [-t dsa | ecdsa | ed25519 | rsa ] [-N new_passphrase ] [-C comment ] [-f output_keyfile ] I may be wrong here, but I think the above argument list would benefit from the inclusion of "-a rounds". It is not immediately apparent that key generation takes "-a rounds" as an argument, although one could argue it is on the manpage and one must read it thoroughly. I confirmed via code that it does, and hence this request. 2) The paragraphs of "-a rounds" documentation might benefit from minor rephrasing: Current "When saving a private key this option specifies the number of KDF (key derivation function) rounds used." Rephrased "When saving a private key, this option specifies the number of key derivation function (KDF) rounds used." Current "When screening DH-GEX candidates (using the -T command). This option specifies the number of primality tests to perform." Rephrased "When screening DH-GEX candidates (using the -T command), this option specifies the number of primality tests to perform." P.S. I had trouble trying to phrase the subject for this mail, apologies for the catchall. Regards, ab -|-|-|-|-|-|-|--
Intel Celeron SoC support
Hi, I am running an ASRock J4105B-ITX board and wanting to run OpenBSD on this. https://www.asrock.com/MB/Intel/J4105B-ITX/index.asp#BIOS It boots up, and at the 'boot>' prompt I can use the keyboard find. However after it boots up, the keyboard stops working, and no disks are found by the installer (used auto_install to send test commands). It appears that there is no chipset support, for the Intel Celeron J4105 CPU from what I can work out. To test that it was working fine and is just OpebBSD which is not working, I installed Linux and have included the dmesg below (from Linux). I cannot run a dmesg from the OpenBSD installer as I cannot use the keyboard etc. Will support come for this SoC architecture? Or am I better of selling this board? Think its a Gemini Lake SoC Chipset; [0.00] Linux version 4.9.0-8-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.130-2 (2018-10-27) [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.9.0-8-amd64 root=/dev/mapper/virt1--vg-root ro quiet intel_iommu=on [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' [0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' [0.00] x86/fpu: xstate_offset[3]: 576, xstate_sizes[3]: 64 [0.00] x86/fpu: xstate_offset[4]: 640, xstate_sizes[4]: 64 [0.00] x86/fpu: Enabled xstate features 0x1b, context size is 704 bytes, using 'compacted' format. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0003dfff] usable [0.00] BIOS-e820: [mem 0x0003e000-0x0003] reserved [0.00] BIOS-e820: [mem 0x0004-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x0fff] usable [0.00] BIOS-e820: [mem 0x1000-0x12150fff] reserved [0.00] BIOS-e820: [mem 0x12151000-0x76d93fff] usable [0.00] BIOS-e820: [mem 0x76d94000-0x7963dfff] reserved [0.00] BIOS-e820: [mem 0x7963e000-0x7968efff] usable [0.00] BIOS-e820: [mem 0x7968f000-0x796b6fff] ACPI NVS [0.00] BIOS-e820: [mem 0x796b7000-0x799eafff] reserved [0.00] BIOS-e820: [mem 0x799eb000-0x79a9bfff] type 20 [0.00] BIOS-e820: [mem 0x79a9c000-0x7a4c1fff] usable [0.00] BIOS-e820: [mem 0x7a4c2000-0x7a56dfff] reserved [0.00] BIOS-e820: [mem 0x7a56e000-0x7abf] usable [0.00] BIOS-e820: [mem 0x7ac0-0x7fff] reserved [0.00] BIOS-e820: [mem 0xd000-0xd0ff] reserved [0.00] BIOS-e820: [mem 0xd3709000-0xd3709fff] reserved [0.00] BIOS-e820: [mem 0xe000-0xefff] reserved [0.00] BIOS-e820: [mem 0xfe042000-0xfe044fff] reserved [0.00] BIOS-e820: [mem 0xfe90-0xfe902fff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed01000-0xfed01fff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00017fff] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.60 by American Megatrends [0.00] efi: ACPI 2.0=0x7968f000 ACPI=0x7968f000 SMBIOS=0x79948000 SMBIOS 3.0=0x79947000 ESRT=0x75cce798 MEMATTR=0x73b5e098 [0.00] SMBIOS 3.1.1 present. [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] e820: last_pfn = 0x18 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 00FF00 mask 7FFF00 write-combining [0.00] 1 base 00 mask 7F8000 write-back [0.00] 2 base 007B00 mask 7FFF00 uncachable [0.00] 3 base 007C00 mask 7FFC00 uncachable [0.00] 4 base 01 mask 7F8000 write-back [0.00] 5 base 009000 mask 7FF000 write-combining [0.00] 6 disabled [0.00] 7 disabled [0.00] 8 disabled [0.00] 9 disabled [0.00] x86/PAT: Configuration
Re: Problem with installing OpenBSD 6.4 on VirtualBox
hello, I upgraded VirtualBox from 5.1 to 5.2 and ... it works ! as the solution was so easy, i feel confused... thanks for your help. Le mar. 13 nov. 2018 à 22:07, jean-yves boisiaud < jean-yves.boisi...@alcor-consulting.fr> a écrit : > hello Dumitru, > > thanks for your answer. > > Le mar. 13 nov. 2018 à 21:50, Dumitru Moldovan a écrit : > >> On Tue, 13 Nov 2018 20:51:09 +0100, jean-yves boisiaud < >> jean-yves.boisi...@alcor-consulting.fr> wrote: >> >> > I 'm trying to install OpenBSD 6.4 on VirtualBox 5.1.38 on a LinuxMint >> host. >> > Please note that 6.0, ... 6.3 worked fine, only 6.4 failed. >> >> I've been running 6.4 with no issues on VirtualBox 5.0.x (initially) and >> now 5.2.x. But it's a VM installed with OpenBSD 5.6 and upgraded over the >> years, not installed from latest stable media. >> >> Judging by the latest releases, the 5.1.x VirtualBox series is out of >> maintenance, and the last 5.1.x version is dated before OpenBSD's 6.4 >> release (the same is true for 5.0.x). Maybe try latest stable release, >> 5.2.22 at the moment? > > > ok, I'll try. > >> And make sure you choose the right OS template when creating the VM? >> > > Yes. BSD - OpenBSD 64 bits. > > >> >> > The boot sequence starts, and restarts forever. >> > >> > I recorded the console of the VM, the last message displayed before >> reboot >> > is : >> > >> > isa0 at mainbus0 >> > pckbc0 at isa0 port 0x60/5 irq 1 irq 12 >> >> These two lines are common on both my VM and my desktop. The next two >> lines are: >> >> pckbd0 at pckbc0 (kbd slot) >> wskbd0 at pckbd0: console keyboard >> >> Uneducated guess here, but is there anything out of normal with your >> keyboard setup in the VM or with the keyboard options chosen during >> install? > > keyboard is the default. > > >> Can you try the defaults? >> > > Yes. 64 still fails and 63 still works... > > I will upgrade VirtualBox to 5.2. and make a try. > > > -- > Jean-Yves Boisiaud - Alcor Consulting > 49, rue du Chemin Vert > 49300 Cholet > mobile : +33 6 63 71 73 46 > -- Jean-Yves Boisiaud - Alcor Consulting 49, rue du Chemin Vert 49300 Cholet mobile : +33 6 63 71 73 46
