Masterwishx

i found that i had sometime my "towername" is gone from the net in Total commander and win explorer in Windows , but if i enter manual i can access, not sure if it is belong to this problem ?

@bonienl can you explain please how new plugin (Safe Mode) work ?

Thats what i runned for nut developer requested :

Wow it shows all the info ! include product and serial :

@SimonF Maybe you can help me with (unknown) problem ,im in tuch with developers of nut they said: Thanks. So, to summarize: even though the driver is running as root, and maybe there are no competitors (who is 6609? was it somehow fuser itself or something else?), libusb in usbhid-ups won't tell the basic iProduct etc. fields used during matching and which lsusb does see, but the driver sees further info from the actual protocol query/response. So a sort of sideways solution could be to ensure these values (if "unknown") by querying something additionally over USB HID protocol, if the device serves those data points. But the primary direct solution would be to find out why they are "unknown" in the first place and avoiding that. And documenting in how-to's for posterity. > fuser /dev/bus/usb/003/002 Cannot stat file /proc/6609/fd/46: Stale file handle /dev/bus/usb/003/002: 7697 i found 6609 its smb deamon , maybe its used becose of netserver ups mode in my case , im using for Windows client (my Main PC) The strange thing i can see all info when running ' lsusb -vv ' : So maybe you can suggest something ?

Thanks, another post was : So the problem is very likely due to that original "libusb can't get the details", which may be a permissions problem or the device being busy due to someone else grabbing it with higher priority (hypervisor, OS drivers and daemons, etc. The strange thing i can see all info when running ' lsusb -vv ' : but device,model is unknown and no serial number :

@SimonF about "unknown 2000" device in my case , i made a debug logs for authors and they ask : (Just in case: are the udev.rules (or udev.hwdb) issues ruled out? Does the OS know to not grab certain VID:PID pairs and/or to re-own them to nut:nut or similar accounts?) Maybe you know about it?

@SimonF can you please check why nut-2.8.0.plg update from "nut-plugin-2023.02.14-x86_64-1" to "nut-plugin-2023.06.03-x86_64-1.txz" and become 2.7.4 in nut-2.8.0.plg ? on 6.12.1 is anyone have update problem also for plugin ? P.S i removed plugin then installed again , and have same problem after autoupdate

i restored v2.8.0 (nut-plugin-2023.02.14-x86_64-1 and nut-2.8.0.plg ) from backup to flash yesterday but after autoupdate its again updated to (nut-plugin-2023.06.03-x86_64-1.txz and nut-2.8.0.plg) that in fact its 2.7.1 ...

After checked the plugin auto updated to nut-plugin-2023.06.03-x86_64-1.txz also file nut-2.8.0.plg but in fact its 2.7.1 ....

After updated to 6.12 version , somehow plugin goes back to 2.7 from 2.8 ... is 2.8 working OK in 6,12 ?

is anyone configured unraid syslog with promtail ?

Did you made a dir befor ?

Also interesting why custom network br0 or br1 in docker does not have internet access from local net ?

changed to br1 docker network without host access ,all was working fine no macvlan traces found . but today somehow founded again !??!

i moved dockers to br1 becose of macvlan problem: befor i had bond0 of two interfaces and they was both in ethernet nics, now only eth0, should i add also eth1 that is docker network ...

its strange but found : Because each watch is a structure, available memory is also a bottleneck for using inotify. In fact, a watch can take up to 1KB of space. This means a million watches could result in 1GB of extra RAM usage. https://www.baeldung.com/linux/inotify-upper-limit-reached Also when changed to 14506750 i didnt saw memory use increased .... for now i was set back to default ...

Yes i know , but i was thinking after disabled the plugin should be less , but after boot today is even more !

Having huge amount of User Watches ,after disabled plugin Fiile Activity still have Current User Watches = 12486295 is it normal size ?

in my case on same hardware was no problems at all about 3 years ,but last month on 6.11.5 kernel traps on syslog with macvlan + host access. on 6.12 got server freeze and macvlan traps , so changed to ipvlan then to this fix (macvlan on br1 + no host access). also got System_cache_ssd xfs filesystem broken with docker.img btrfs error , maybe not related ... so fixed xfs and deleted docker image ... so now i have strange br0 behavior on syslog every some minutes : Also strange docker alocation of proxynet instead of 172.18.0.x , maybe this is just the bug of 6.12.1 ?

its working After reset button + scale to 90% from 110% in my case 2560x1440 screen , in 6.11.5 i think was 3 column in 110%

For VLAN we need router or switch with VLAN support

@Squid was fixed this plugin in past, maybe he can fix it again if he has time for it...

@bonienl @mikl im a little confused : ipvlan + no host access = this solution ( macvlan + no host access on br1 ) but if host access enabled then its not working ? im had issue on 6.11.5 with macvlan call traces found only in syslog ,on 6.12 also having in syslog also server crashed yesterday, using macvlan + host access ... So the problem with macvlan or when macvlan + host access enabled or needs to be checked in every user case ?

Sorry, english not my first lang, How to do it ? i cant find setting for this...