mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
Motion notification via email - no picture attached #1818
Labels
No labels
Android app
Arch Linux
CI/CD
CSS
FreeBSD
HTML/HTTP
Home Assistant addon
JavaScript
Python
Raspberry Pi
Stale No Activity 60 Days
bug
code format
dependencies
dev branch
docker
documentation
duplicate
enhancement
feature
help wanted
i18n/l10n
invalid
legacy motionEye
meta
motion
motionEyeOS
notourproblem
python update
question
question
security
troubleshooting
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/motioneye#1818
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mireksochor on GitHub (Nov 24, 2020).
Hi and thank you for such a great piece of SW, really appreciate the hard work you put into MotionEye.
I have fresh install in Rpi 3B, all configured, working well except no pictures attached to email.
My settings is:
motionEye Version | 0.42.1
Motion Version | 4.2.2+gitUNKNOWN
OS Version | motionEyeOS 20200606
No FTP or Samba, SSH enabled only
Text overlay: ON
Video Streaming: OFF
Still images: ON
Capture Mode:motion triggered
Movies: OFF
Motion detection: ON
Auto treshold: ON
Auto Noise detection: ON
Light switch detection: 0%
Despeckle filter:ON
Motion gap: 5s
Capture before: 1frame
Capture after: 1frame
Minimum motion frames: 20frames
Motion notification: Send and email: ON
Attached Pictures Time Span: 5s
I can see photos being taken and stored, but emails has no attachment.
I am using gmail as SMTP server.
Thank you for help,
M.
@starbasessd commented on GitHub (Nov 24, 2020):
Please include logs: dmesg, messages.log, motioneye.log.
Do you have a lot of pictures being stored on the Pi in question?
Also consider using 20190911, 20200203, or dev20201026.
The motionEyeOS support pages are over at
Home · ccrisan/motioneyeos Wiki
https://github.com/ccrisan/motioneyeos/wiki
On Tue, Nov 24, 2020 at 11:38 AM Smirek notifications@github.com wrote:
--
Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52"
W85° 45' 8.56"
Semper Gumby
“Don't tell people how to do things. Tell them what to do and let them
surprise you with their results.” - G.S. Patton, Gen. USA
Ethics are what we do when no one else is looking.
Quis custodiet ipsos custodes?
“There is no end to the good you can do if you don’t care who
gets the credit.” - C Powell
You know we're sitting on four million pounds of fuel, one nuclear weapon
and a thing that has 270,000 moving parts built by the lowest bidder. Makes
you feel good, doesn't it?
@mireksochor commented on GitHub (Nov 25, 2020):
Hi!
there is less than 20 pictures stored.
Logs bellow:
motioneye.log
2020-11-24 12:28:42: [sendmail] INFO: sending email
2020-11-24 12:28:44: [sendmail] INFO: email sent
2020-11-24 13:35:14: [sendmail] INFO: sending email
2020-11-24 13:35:15: [sendmail] INFO: email sent
2020-11-24 13:35:56: [sendmail] INFO: sending email
2020-11-24 13:35:57: [sendmail] INFO: email sent
2020-11-24 17:10:30: [motioneye] WARNING: 403 GET /login/?_=1606234230239&username=&_signature=3b4750a5429cacaaefcad27bdfd4be2558fc029f (10.0.1.171) 5.02ms
2020-11-24 17:25:06: [motioneye] WARNING: mjpg client connection for camera 2 on port 8082 is closed
dmesg.log
---- booting motionEyeOS 20200606 ----
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.19.83-v7 (root@a49a11003f4f) (gcc version 8.2.1 20180802 (GNU Toolchain for the A-profile Architecture 8.2-2018.11 (arm-rel-8.26))) #1 SMP Sat Jun 6 14:14:33 UTC 2020
[ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 8 MiB at 0x2f800000
[ 0.000000] On node 0 totalpages: 196608
[ 0.000000] Normal zone: 1728 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 196608 pages, LIFO batch:63
[ 0.000000] random: get_random_bytes called from start_kernel+0xb0/0x4b4 with crng_init=0
[ 0.000000] percpu: Embedded 16 pages/cpu s36684 r8192 d20660 u65536
[ 0.000000] pcpu-alloc: s36684 r8192 d20660 u65536 alloc=16*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 194880
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.fiq_fix_enable=1 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait ro rootflags=noload panic=10 quiet loglevel=1
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 756380K/786432K available (8192K kernel code, 655K rwdata, 2228K rodata, 1024K init, 820K bss, 21860K reserved, 8192K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xb0800000 - 0xff800000 (1264 MB)
lowmem : 0x80000000 - 0xb0000000 ( 768 MB)
modules : 0x7f000000 - 0x80000000 ( 16 MB)
.text : 0x(ptrval) - 0x(ptrval) (9184 kB)
.init : 0x(ptrval) - 0x(ptrval) (1024 kB)
.data : 0x(ptrval) - 0x(ptrval) ( 656 kB)
.bss : 0x(ptrval) - 0x(ptrval) ( 821 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 26874 entries in 79 pages
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[ 0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[ 0.000018] Switching to timer-based delay loop, resolution 52ns
[ 0.000280] Console: colour dummy device 80x30
[ 0.000299] console [tty1] enabled
[ 0.000338] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[ 0.000355] pid_max: default: 32768 minimum: 301
[ 0.000676] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000691] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001627] CPU: Testing write buffer coherency: ok
[ 0.002086] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002732] Setting up static identity map for 0x100000 - 0x10003c
[ 0.002883] rcu: Hierarchical SRCU implementation.
[ 0.003671] smp: Bringing up secondary CPUs ...
[ 0.004505] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.005446] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.006307] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.006432] smp: Brought up 1 node, 4 CPUs
[ 0.006443] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[ 0.006449] CPU: All CPU(s) started in HYP mode.
[ 0.006454] CPU: Virtualization extensions available.
[ 0.007389] devtmpfs: initialized
[ 0.020306] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[ 0.020543] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.020563] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.021162] pinctrl core: initialized pinctrl subsystem
[ 0.022014] NET: Registered protocol family 16
[ 0.024989] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[ 0.030632] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.030639] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.030834] Serial: AMBA PL011 UART driver
[ 0.033096] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[ 0.067911] bcm2835-dma 3f007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1
[ 0.069550] SCSI subsystem initialized
[ 0.069764] usbcore: registered new interface driver usbfs
[ 0.069819] usbcore: registered new interface driver hub
[ 0.069919] usbcore: registered new device driver usb
[ 0.090123] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-11-14 15:27, variant start_x
[ 0.100354] raspberrypi-firmware soc:firmware: Firmware hash is 2354eac70a98807e06bed2149bc0c5613e751c15
[ 0.111762] clocksource: Switched to clocksource arch_sys_counter
[ 0.202871] VFS: Disk quotas dquot_6.6.0
[ 0.202955] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.203138] FS-Cache: Loaded
[ 0.203346] CacheFiles: Loaded
[ 0.213292] NET: Registered protocol family 2
[ 0.214123] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[ 0.214160] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.214270] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.214455] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.214594] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.214644] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.214876] NET: Registered protocol family 1
[ 0.215457] RPC: Registered named UNIX socket transport module.
[ 0.215463] RPC: Registered udp transport module.
[ 0.215469] RPC: Registered tcp transport module.
[ 0.215474] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.216800] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[ 0.219830] Initialise system trusted keyrings
[ 0.220020] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[ 0.229754] FS-Cache: Netfs 'nfs' registered for caching
[ 0.230309] NFS: Registering the id_resolver key type
[ 0.230334] Key type id_resolver registered
[ 0.230341] Key type id_legacy registered
[ 0.230357] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.232748] Key type asymmetric registered
[ 0.232757] Asymmetric key parser 'x509' registered
[ 0.232828] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 0.232988] io scheduler noop registered
[ 0.232995] io scheduler deadline registered
[ 0.233182] io scheduler cfq registered (default)
[ 0.233190] io scheduler mq-deadline registered
[ 0.233197] io scheduler kyber registered
[ 0.236473] bcm2708_fb soc:fb: FB found 1 display(s)
[ 0.245432] Console: switching to colour frame buffer device 82x26
[ 0.249858] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 656x416
[ 0.252025] bcm2835-rng 3f104000.rng: hwrng registered
[ 0.252362] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[ 0.252846] vc-sm: Videocore shared memory driver
[ 0.253180] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[ 0.263876] brd: module loaded
[ 0.273869] loop: module loaded
[ 0.274464] Loading iSCSI transport class v2.0-870.
[ 0.275146] libphy: Fixed MDIO Bus: probed
[ 0.275248] usbcore: registered new interface driver lan78xx
[ 0.275304] usbcore: registered new interface driver smsc95xx
[ 0.275320] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 0.303164] dwc_otg 3f980000.usb: base=(ptrval)
[ 0.503395] Core Release: 2.80a
[ 0.503404] Setting default values for core params
[ 0.503431] Finished setting default values for core params
[ 0.703723] Using Buffer DMA mode
[ 0.703730] Periodic Transfer Interrupt Enhancement - disabled
[ 0.703735] Multiprocessor Interrupt Enhancement - disabled
[ 0.703744] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 0.703757] Dedicated Tx FIFOs mode
[ 0.704218] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = af904000 dma = 0xef904000 len=9024
[ 0.704243] FIQ FSM acceleration enabled for :
Non-periodic Split Transactions
Periodic Split Transactions
High-Speed Isochronous Endpoints
Interrupt/Control Split Transaction hack enabled
[ 0.704250] dwc_otg: Microframe scheduler enabled
[ 0.704305] WARN::hcd_init_fiq:457: FIQ on core 1
[ 0.704317] WARN::hcd_init_fiq:458: FIQ ASM at 8067bbe4 length 36
[ 0.704329] WARN::hcd_init_fiq:497: MPHI regs_base at b0810000
[ 0.704345] dwc_otg 3f980000.usb: DWC OTG Controller
[ 0.704394] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[ 0.704427] dwc_otg 3f980000.usb: irq 56, io mem 0x00000000
[ 0.704475] Init: Port Power? op_state=1
[ 0.704480] Init: Power Port (0)
[ 0.704718] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 0.704730] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.704739] usb usb1: Product: DWC OTG Controller
[ 0.704748] usb usb1: Manufacturer: Linux 4.19.83-v7 dwc_otg_hcd
[ 0.704758] usb usb1: SerialNumber: 3f980000.usb
[ 0.705373] hub 1-0:1.0: USB hub found
[ 0.705434] hub 1-0:1.0: 1 port detected
[ 0.706020] dwc_otg: FIQ enabled
[ 0.706026] dwc_otg: NAK holdoff enabled
[ 0.706031] dwc_otg: FIQ split-transaction FSM enabled
[ 0.706042] Module dwc_common_port init
[ 0.706317] usbcore: registered new interface driver usb-storage
[ 0.706490] mousedev: PS/2 mouse device common for all mice
[ 0.707341] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[ 0.707546] bcm2835-cpufreq: min=600000 max=1200000
[ 0.708031] sdhci: Secure Digital Host Controller Interface driver
[ 0.708037] sdhci: Copyright(c) Pierre Ossman
[ 0.708409] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
[ 0.708790] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[ 0.708921] sdhci-pltfm: SDHCI platform and OF driver helper
[ 0.710384] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.710562] hidraw: raw HID events driver (C) Jiri Kosina
[ 0.710692] usbcore: registered new interface driver usbhid
[ 0.710698] usbhid: USB HID core driver
[ 0.711592] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
[ 0.713113] [vc_sm_connected_init]: start
[ 0.721697] [vc_sm_connected_init]: end - returning 0
[ 0.723104] Initializing XFRM netlink socket
[ 0.723132] NET: Registered protocol family 17
[ 0.723236] Key type dns_resolver registered
[ 0.723741] Registering SWP/SWPB emulation handler
[ 0.724400] registered taskstats version 1
[ 0.724416] Loading compiled-in X.509 certificates
[ 0.731553] uart-pl011 3f201000.serial: cts_event_workaround enabled
[ 0.731627] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 81, base_baud = 0) is a PL011 rev2
[ 0.733558] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
[ 0.733569] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
[ 0.759792] sdhost: log_buf @ (ptrval) (ef907000)
[ 0.795238] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 0.796828] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 0.798411] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 0.801254] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 0.809339] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[ 0.810678] of_cfs_init
[ 0.810836] of_cfs_init: OK
[ 0.811429] Waiting for root device /dev/mmcblk0p2...
[ 0.868606] mmc0: host does not support reading read-only switch, assuming write-enable
[ 0.871457] mmc0: new high speed SDHC card at address 0007
[ 0.872795] mmcblk0: mmc0:0007 Y016B 14.9 GiB
[ 0.873956] random: fast init done
[ 0.874839] mmcblk0: p1 p2 p3
[ 0.898241] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: noload
[ 0.898291] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 0.898941] devtmpfs: mounted
[ 0.903542] Freeing unused kernel memory: 1024K
[ 0.914824] mmc1: new high speed SDIO card at address 0001
[ 0.932159] Run /sbin/init as init process
[ 0.932246] Indeed it is in host mode hprt0 = 00021501
[ 1.141824] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 1.141959] Indeed it is in host mode hprt0 = 00001101
[ 1.382325] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
[ 1.382357] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.383588] hub 1-1:1.0: USB hub found
[ 1.383731] hub 1-1:1.0: 5 ports detected
[ 1.701818] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 1.832082] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[ 1.832097] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.834930] smsc95xx v1.0.6
[ 1.925044] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:e4:ef:18
[ 5.723909] EXT4-fs (mmcblk0p3): recovery complete
[ 5.726929] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[ 6.089052] media: Linux media interface: v0.10
[ 6.121044] videodev: Linux video capture interface: v2.00
[ 6.148130] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.150478] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[ 6.150490] [vc_sm_connected_init]: start
[ 6.150982] [vc_sm_connected_init]: installed successfully
[ 6.154648] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.160363] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[ 6.793400] bcm2835-v4l2: scene mode selected 0, was 0
[ 6.793756] bcm2835-v4l2: V4L2 device registered as video0 - stills mode > 1920x1200
[ 6.798748] bcm2835-v4l2: Broadcom 2835 MMAL video capture ver 0.0.2 loaded.
[ 6.886342] i2c /dev entries driver
[ 7.401881] udevd[292]: starting version 3.2.7
[ 7.427349] random: udevd: uninitialized urandom read (16 bytes read)
[ 7.428860] random: udevd: uninitialized urandom read (16 bytes read)
[ 7.428975] random: udevd: uninitialized urandom read (16 bytes read)
[ 7.471537] udevd[295]: starting eudev-3.2.7
[ 7.648681] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.667452] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[ 7.667513] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[ 7.674966] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[ 7.675012] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[ 7.680773] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[ 7.680815] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[ 7.718816] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 7.737278] bcm2835_audio soc:audio: card created with 8 channels
[ 7.885528] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 8.111687] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 8.171391] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[ 8.177065] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 8.177332] usbcore: registered new interface driver brcmfmac
[ 8.392223] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[ 8.392375] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[ 8.393235] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[ 8.518779] random: crng init done
[ 8.518795] random: 2 urandom warning(s) missed due to ratelimiting
[ 8.916063] brcmfmac: power management disabled
[ 9.146333] brcmfmac: power management disabled
[ 9.831894] Under-voltage detected! (0x00050005)
[ 10.623863] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 22.181419] NET: Registered protocol family 10
[ 22.188140] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 22.189476] Segment Routing with IPv6
[ 22.598554] system date is 2020-11-23 17:41:25
Messasges.log
shortened for repeating throttlewatch message.
Nov 24 17:13:00 meye-e8e4ef18 cron.info crond[1141]: USER root pid 23105 cmd /usr/sbin/logrotate /etc/logrotate.conf
Nov 24 17:13:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 39 C
Nov 24 17:14:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 40 C
Nov 24 17:15:00 meye-e8e4ef18 cron.info crond[1141]: USER root pid 23318 cmd /usr/sbin/dyndns-update
Nov 24 17:15:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 41 C
Nov 24 17:15:29 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /data/etc/motion.conf
Nov 24 17:15:29 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] config_camera: Processing camera config file camera-2.conf
Nov 24 17:15:29 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Logging to syslog
Nov 24 17:15:29 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Motion 4.2.2+gitUNKNOWN Started
Nov 24 17:15:29 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
Nov 24 17:15:29 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (WRN)
Nov 24 17:16:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 40 C
Nov 24 17:17:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 40 C
Nov 24 17:17:36 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /data/etc/motion.conf
Nov 24 17:17:36 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] config_camera: Processing camera config file camera-2.conf
Nov 24 17:17:36 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Logging to syslog
Nov 24 17:17:36 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Motion 4.2.2+gitUNKNOWN Started
Nov 24 17:17:36 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
Nov 24 17:17:36 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (WRN)
Nov 24 17:18:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 40 C
Nov 24 17:19:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 39 C
Nov 24 17:20:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 39 C
Nov 24 17:21:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 39 C
Nov 24 17:22:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 39 C
Nov 24 17:23:16 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 40 C
Nov 24 17:24:17 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 40 C
Nov 24 17:24:18 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /data/etc/motion.conf
Nov 24 17:24:18 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] config_camera: Processing camera config file camera-2.conf
Nov 24 17:24:18 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Logging to syslog
Nov 24 17:24:18 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Motion 4.2.2+gitUNKNOWN Started
Nov 24 17:24:18 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
Nov 24 17:24:18 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (WRN)
Nov 24 17:25:04 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /data/etc/motion.conf
Nov 24 17:25:04 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] config_camera: Processing camera config file camera-2.conf
Nov 24 17:25:04 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Logging to syslog
Nov 24 17:25:04 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Motion 4.2.2+gitUNKNOWN Started
Nov 24 17:25:04 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
Nov 24 17:25:04 meye-e8e4ef18 user.notice motion: [0:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (WRN)
Nov 24 17:25:17 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 41 C
Nov 24 17:26:17 meye-e8e4ef18 user.notice throttlewatch: currently: under-voltage throttled , temperature: 39 C
@starbasessd commented on GitHub (Nov 25, 2020):
In messages.log first thing I notice is you have a bad/underpowered power
supply. Throttling causes all kinds of problems. The board is trying to
protect itself.
If you can ssh in or use the console. run the command:
logrotate -f /etc/logrotate.conf [enter]
Wait 24 hours, then download and attach the complete log files to the
\https://github.com/ccrisan/motioneye/issues/1956
incident ticket. You can download the logs from the Settings, Expert
Settings, section of the WebGUI.
On Wed, Nov 25, 2020 at 3:36 AM Smirek notifications@github.com wrote:
--
Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52"
W85° 45' 8.56"
Semper Gumby
“Don't tell people how to do things. Tell them what to do and let them
surprise you with their results.” - G.S. Patton, Gen. USA
Ethics are what we do when no one else is looking.
Quis custodiet ipsos custodes?
“There is no end to the good you can do if you don’t care who
gets the credit.” - C Powell
You know we're sitting on four million pounds of fuel, one nuclear weapon
and a thing that has 270,000 moving parts built by the lowest bidder. Makes
you feel good, doesn't it?
@mireksochor commented on GitHub (Nov 25, 2020):
Thank you for pointing that out @starbasessd. The underpower is quite unprobable as I tried 3 microUSB cables and 2 power bricks (18W apple charger and 12W power charger) and Raspi never take more than 700mA on 5.2V when I tested. It has small fan installed, but no cooler. I will try previous OS release and see if I can make it work.
@starbasessd commented on GitHub (Nov 25, 2020):
"Chargers" are never a good thing(TM). They have current limiting circuitry
and charging circuitry built in that the PI can't talk to. (especially
Apple products).
I have a number of official RPi power supplies, and a number of other power
supplies that don't have issues (2.5a or larger) 3 'chargers' (15 W or
better) all have issues with Pis, even PiZero. All work to spec with
devices requiring 'chargers'.
On Wed, Nov 25, 2020 at 8:22 AM Smirek notifications@github.com wrote:
--
Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52"
W85° 45' 8.56"
Semper Gumby
“Don't tell people how to do things. Tell them what to do and let them
surprise you with their results.” - G.S. Patton, Gen. USA
Ethics are what we do when no one else is looking.
Quis custodiet ipsos custodes?
“There is no end to the good you can do if you don’t care who
gets the credit.” - C Powell
You know we're sitting on four million pounds of fuel, one nuclear weapon
and a thing that has 270,000 moving parts built by the lowest bidder. Makes
you feel good, doesn't it?
@zagrim commented on GitHub (Nov 25, 2020):
Just a thought about the undervoltage and the fan you mentioned: Even a small fan drains relatively lot of current, and if the fan is powered through the Pi it still might overload the capacity of the Pi. Myself I had stability issues on a Pi2 with a extension board (powered through the Pi2) and a USB Wifi adapter until I plugged the extension board to a separate power supply even though I was already using a USB power supply with the output something like 2.1 - 2.5 A (10.5 - 12.5). Pi2 uses less power itself, but might also be more limited than Pi3 WRT supplying power to other devices, so this will not directly match your specs, but hopefully makes my point clear, though.
@zagrim commented on GitHub (Nov 25, 2020):
Regarding the topic issue, there's this: https://github.com/ccrisan/motioneyeos/wiki/FAQ#what-should-i-do-to-have-pictures-attached-to-motion-notification-emails
I have myself also experienced this, most of the notifications never had any picture, and as far as I've understood that's because the email is sent before the snapshot image is produced in some cases. I'm pretty sure there's been a issue explaining the details around that but I can't find it now. Basically that would be due to the snapshot being saved to the disk only after the capture ends (in case of saving the "best" picture) and there being a sort of a race condition between that and the email sending process.
@mireksochor commented on GitHub (Nov 26, 2020):
Thanks @zagrim, I appreciate your explanation. I have found the power source that is just 1.5A but RasPi is not complaining.
You very well described my thoughts, thank you for that, regarding the timing of email being sent and snapping the photo. Is there any way how to set wait time for the photo? Or make and condition that email without attachment wont leave?
@zagrim commented on GitHub (Nov 26, 2020):
My explanation was still only guessing based on something someone has written here, at some point (now that was vague, uh :) ). Anyway, since it is an extenal process (Motion) running which is saving the files, in continuously parallel with ME, it's not that easy to tell when is has finished its job. Unless I remember it wrong, when ME is configured with Capture Mode = Motion Triggered (One Picture), what Motion does is to scan through to captured frames to find the one with highest amount of changed pixels and then save that. On a RPi that might take a while, depending on the framerate and video length & quality.
One thing you could try is to increase the "Attached Pictures Time Span" under notification settings to see if that would be a key to success. At least that setting should directly impact how long the email sending waits before searching for files to attach.
If that doesn't help, the only thing I can come up with at the moment is to increase logging verbosity to "debug" (
log_levelinmotioneye.conf) and then inspect themotioneye.log(attach it here) after motion has been detected - and the changing the log level back to "info" to avoid bloating the logs. From the logs it should be, hopefully, possible to see if the email is actually sent before the picture has been saved.@starbasessd commented on GitHub (Nov 26, 2020):
in /etc/motioneye/motioneye.conf there is a parameter:
list_media_timeout_email 10
that you could increase by 10 until you get consistent attachments...
On Thu, Nov 26, 2020 at 11:46 AM Esa Tikka notifications@github.com wrote:
--
Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52"
W85° 45' 8.56"
Semper Gumby
“Don't tell people how to do things. Tell them what to do and let them
surprise you with their results.” - G.S. Patton, Gen. USA
Ethics are what we do when no one else is looking.
Quis custodiet ipsos custodes?
“There is no end to the good you can do if you don’t care who
gets the credit.” - C Powell
You know we're sitting on four million pounds of fuel, one nuclear weapon
and a thing that has 270,000 moving parts built by the lowest bidder. Makes
you feel good, doesn't it?
@zagrim commented on GitHub (Nov 26, 2020):
Yes, that, too, although the logs should indicate with an error if that timeout is reached when searching for media files.
@starbasessd commented on GitHub (Mar 5, 2021):
No response in >30 days. If you are still having issues, please open a new issue.