Jump to content

KYTECHNGAMING

Forum Members
  • Posts

    641
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by KYTECHNGAMING

  1. 24 minutes ago, vst said:

    @KYTECHNGAMING Does this issue reproduce when only one camera is backing up?

    Hi @vst

    I didn't make any setting changes. I upgraded to Keenetic 4.0.A.15.
    I can say "yes" to the answer to your question. Dailybackup is active. It reboots once a day in xx:20 time zone.

    On the other hand, the other camera transfers hourly backups via smb.

    - There is a separate user authorization for SMB access. (I think you asked me to try without ACL in your previous message. So should I give folder permission with the admin user? If you get back to me about this, I can also perform the tests you want.)

  2. It seems so complicated that it is forgotten while trying to read and understand it.

     

    What are your DHCP blocks?

    What are the installation modes of the devices?

    There is probably a typological error.

     

    -------------------------------------------------------------------------------------

     

    O kadar karışık görünüyor ki, okuyup bir yandan anlamaya çalışırken unutuluyor. 

     

    DHCP bloklarınız nedir? 

    Cihazların kurulum modları nedir? 

    Muthemelen tapolojik hata mevcut. 

  3. On 3/20/2023 at 2:49 PM, vst said:

    @KYTECHNGAMING Thank you for gathering diagnostic information! Ticket SYS-800 has been created. All necessary information is provided to the TSMB service provider.

    We are waiting for answer.

    It would be reasonable to check if the issue is reproduced when ACL component is not installed.

     

    Hello,

    I've been making observations for the problem for 1-2 days. And I thought I didn't write some things.

    I'm accessing the network disk for file transfer to mi cameras with a different user in keenetic. (I think you already wrote ACL because of this.)
    This user only has SMB privileges and permissions to that disk/folder. (Are you suggesting that I access it with admin?)


    There are two of these cameras. Both create separate folder tree. 
    The settings are exactly the same. Only the backup syncs are different. Hourly vs Daily 
    Same sdcards mounted. There is no problem recording to SDcard. Although the technical data writes that the support is maximum 32gb sdcard, 128gb sdcard works.
    They are connected to the same repeater on my Keenetic Mesh system. https://prnt.sc/Qm9tgBmcwmwh

    One of them continues the backup to the same disk properly..(Misak) 
    The other one has already stop the backup along with the reboot issue.(Lal) See the dates of the files in the most recent folders in SMB. (2. folder @ x-plore video) https://disk.yandex.com.tr/i/tKNSVv5NRjht3Q

    I turned off a feature in the Mi settings about 48 hours ago. He's not making a backup. Anyway, I don't understand exactly what the setting says, either. :) https://disk.yandex.com.tr/i/R9gQ8s2JjNiZJA

    But the restart problem seems to have disappeared now.

    - I'm not sure, but the camera that created this reboot problem also reboots itself. Just like I couldn't access the videos on the sdcard while recording the phone screen, while writing this article, I noticed that Keenetic was offline in the device list and online after a while.

    - The screen recordings also recorded music in the background. Don't forget to turn down the video volume.

     

     

     

    • Upvote 2
  4. 40 minutes ago, sergeyk said:

    Unfortunately syslog messages are not enough. It is need the packet dump saved at the crash moment.

    Could you use the tcpdump utility in an unbuffered mode from opkg?

    tcpdump -U -w /<path-to-usb-storage/tsmb_crash.pcap port 445 >/dev/null 2>&1

     

    tcpdump installed.
    I started the command as follows. https://prnt.sc/XmgjzXZOa7nk



    The .pcap file was created on disk, but its content is empty. Is he listening now? Isn't it this way?

  5. In the previous message, I showed that the 1st camera was stuck in the past date and time.. @sergeyk
    I set the sync to "Live" to see if we can trigger the issue.

    At 13:20 the syslog record was captured. Router restarted. (Also, no recording has been transferred to my disk.)

    https://prnt.sc/Mng0ahPTdf-a

    Time: Mar 15 13:20:00
    IP: 10.101.0.1
    Host: Keenetic-8178
    Facility: kern
    Priority: crit
    Tag: kernel
    Message: CPU 0 Unable to handle kernel paging request at virtual address 00000000, epc == 9ac62b40, ra == 9ac523c0
    Time: Mar 15 13:20:00
    IP: 10.101.0.1
    Host: Keenetic-8178
    Facility: kern
    Priority: warning
    Tag: kernel
    Message: Oops[#1]:
    Time: Mar 15 13:20:00
    IP: 10.101.0.1
    Host: Keenetic-8178
    Facility: kern
    Priority: warning
    Tag: kernel
    Message: CPU: 0 PID: 718 Comm: vfs-ctrl-650e00 Tainted: P           O    4.9-ndm-5 #0

    Why is the date and time sorting messed up in syslog?
    log time: https://prnt.sc/h9StW35odgvG https://prnt.sc/le1G9a2n4VW5

  6. 23 minutes ago, sergeyk said:

    @KYTECHNGAMING looks like the root cause of reboots is a tsmb module crash (see proc:mtdoops/ndm section in your self-tests).

    "oops": { 
    "origin": "kernel",
    "version":"4.00.A.13.0-0",
    "board": "KN-1011",
    "timestamp": "2023-03-14 00:19:58",
    "hash": "b6d5955",

    and

    "oops": { 
    "origin": "kernel",
    "version":"4.00.A.13.0-0",
    "board": "KN-1011",
    "timestamp": "2023-03-15 00:19:59",
    "hash": "9e603c3a",

    Could you investigate what happens at this time in your network? I do not see any configured schedules in your startup configuration.

    Probably a packet capture for a TSMB protocol close to this time will help (a packet capture should be stored on a USB storage to keep it in a case of a kernel crash).

    Hello sergeyk,

    Yes, I don't have any scheduler.

    It has been going on for 4 nights.
    I'm going to open syslog today.

    According to your findings; At that hour, I think it might just be my Mi camera transferring its backup to disk.

  7. Hello,

    I am using KN-1011-EU.

    The other day, I noticed that the system uptime and WAN IP are different when WG tunnel is not working. I did a check last night.
    One day after installing 4.0.A.13, the main router would reboot at the same time every night.

    03:21 AM There is a reboot action for 3 nights.
    It was 5:30 AM when I took the self-test last night.

    Shared privately.

    Mobile App Events:
    https://prnt.sc/UdtNjez27gl_ https://prnt.sc/9h6omMLjKT4K https://prnt.sc/1C1yJbbdY9F1

    Logs:
    https://prnt.sc/fDi3BAsl_Hn5 https://prnt.sc/0kVjoZbKXors (SOC power status - not sure if it shows physical or software.)

     

     

×
×
  • Create New...