fabbronet

It's a permission issue, with: chmod -R 777 /var/log Syslog started to fill up. Same thing with mongodb and many other daemons. Few apt-updates ago I didn't have this problem but I still don't know what caused the issue...maybe log2ram...

Hi @teenytinycactus, I lowered maximum frequency down to 816MHz and I didn't experienced any random crash from that moment. I think that lowering frequency did the trick but in the same "moment" I found some crashes of mongodb server that's installed on my system. I think that mongo was not the problem but that's it. At this time I'm fighting with log2ram that fills up to 100% messing up everything on reboot because most services see that as a write protection for their own log files, actually I don't know if tweak the logrotate or the log2ram maximum storage dimension....any advice?

I never tried to use directly the GPIO with c/c++ but I skipped the whole hassle to find a working overlay using an 8 way i2c GPIO port expander. If you have electronic skills you can buy this chip: http://www.ti.com/lit/ds/symlink/tca9554.pdf and make a board for it or you can go with a plug&play alternative like this: https://www.abelectronics.co.uk/p/54/IO-Pi-Plus You can manage the the i2c bus enabling it's overlay (add in /boot/armbianEnv.txt overlays=i2c0), install i2ctools (apt-get install i2c-tools) and smbus2 library for python (pip install...) good luck!

It crashed while I was writing! System is still up but network interface is unreachable, I tried with serial and it's very slow. I managed to enter and htop says tath it's all ok but if I look at my journalctl there's something new: Can someone tell me if these lines that I found are someway related to my problem? Now I lowered the CPU frequency to max 816MHz ad started up again....yeee

ok, considering the large number of followers and repliers to my post above I think that is time to give you an update In the last two days I spent about 30 hours on log digging, test and errors and so on...I'm quite tired of this board. System keeps resetting randomly: a ) without the usb breakout board b ) without the external wifi dongle c ) powered from usb d ) powered from GPIO d) with another brand new sd card with a copy of the previous one e) with different power supplies (included a bench 0-30V 0-10A psu) f) with a complete armbian upgrade from 5.38 to 5.41 The only thing that I found is that resets happens most frequently when I'm using an external mongodb client to watch my DB data but from logs I found nothing that point on this. So...I took out the original mongodb installed from repositories (it's old and not mantained as written on mongodb site) and I installed a brand new 3.6.3 version. Now my opi is on and I'm at the 9th hour of uptime but without the external wifi dongle. Now my last three options are: 1) lower the cpu frequency that is almost nailed at 1152Mhz to maybe 816Mhz as I read on this forum to increase kernel stability...is this correct? 2) try another spare board...maybe this one is someway defective 3) try to put the system on the emmc but I already tried and the process failed, probably because I'm trying to put an 8gb sd on an 8gb mmc, I'll try to shrink my sd with gparted and repeat the nand-sata-install... After these three options, if nothing change I'll switch to a raspberry platform that costs more but seems more stable. I'm a first-hour raspberry user and I never had problems like these, under my desktop there's a raspberry up since 2014 so I think that If I'm looking for a reliable solution it's better to switch on rpi. Looking the whole experience as a "street-man" user I can't understand why sunxi put so much effort on building a complex SoC hardware and didn't support it with an adequate system distro like raspberry did with raspbian...in my view this is a big handicap that surely will cut orange market share. I appreciate a lot the armbian's team work but I know that if the whole thing is done freely in your spare time within a small community, the firmware-software support will be always difficult. Stay tuned! cheers

Just a daily update: I checked voltages on the board testpoints with a digital oscilloscope and they're ok, now my suspects are on the external wifi dongle mounted on the breakout board, the board becomes hotter than the cpu (that's quite cool anyway) so maybe is the breakout board design that can't withstand currents drawn by the usb dongle generating a kind of "brown-out" on the main 5V voltage or other weird behaviours. Second suspect is on the micro-sd on wich I'm running the os, I'll give a try to nand-sata-install to see if something change. Today I verified also connections from my custom board and the orange pi board and everything is ok, now I'm trying running my script with usb-wifi dongle unplugged, if everything works fine for a couple of days (that never happened) is that my problem, if it resets randomly again I'll try with the emmc install. By the way, today I also mounted a 200uF 35V electrolytic capacitor on the 5V line, if my problems are from power glitches this solution could fit. Any help is greatly appreciated!

Hi everyone, I have an armbian 5.38 headless system on an orange pi zero2plus board. Attached to this board there's the expansion usb board with a wifi dongle and another board connected to twi interface of the gpio header. I power supply the board from the same header with a 5V 5A power supply, I verified and I have no holes on 5V and 3.3V voltage. The external usb dongle is configured as AP with nmcli, the internal wifi board is configured as w-station and is hooked to my home network. On this system is running a python-flask-uwsgi "daemon" that I'm developing. Well, randomly my system hangs, I can't connect to my flask web page, I can't connect via ssh from putty, if I plug an usb cable my windows system says that device is not recognized so I can't access from serial port with ssh too. The only way is cycle power and start again. I've tried without the usb dongle, with other PSUs and I checked the ssd integrity...everything seems fine. This can happen one hour or 30 hours after boot, it's random. If I look to my journalctl I can't find anything beacuse it flushes every startup so I looked at my syslog, here is an extract of what happens: If i look to my python script log something curious happens meanwhile, my scipt continues running until 7.35am (70 minutes after my log is muted) than stops without errors, it mutes like the syslog Here are my system infos: Here is my armbianmonitor -c "$HOME" output: PS: about the long story I'm in Italy, it's great we have sea, sun and good meals but we also have wifi routers that use channels 12 and 13. My router has the "IT" as wifi regulation policy. So when my router that has the "auto" channel setting, switch to a channel forbidden to orange I loose connection and AP discovery. On orange country is not defined, i found it with: So I tried with: It works...until reboot then it goes again to 00. The workaround I found was to modify /etc/default/crda with REGULATION=IT from that moment I got that error.... I know that if i set the router to work on a fixed channel it works anyway but I can't go this way. thanks a lot for all of your work and efforts!