You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the example code (SimpleLoggingESP8266) running on an ESP32 and either Visual Syslog Server and tftpd64 on windows the first message I actually receive is "This is info message no. 1". This skips over the first 2 messages however after the first loop all messages are sent.
Anyone have any idea why this happens, I have tried adding a large delay and several messages in setup yet no change.
192.168.1.22 Jun 02 18:31:33 1 kern info - my-device my-app - - - This is info message no. 1 192.168.1.22 Jun 02 18:31:33 1 daemon info - my-device my-app - - - This is daemon info message no. 1 192.168.1.22 Jun 02 18:31:33 1 kern info - my-device my-app - - - End loop 192.168.1.22 Jun 02 18:31:42 1 kern info - my-device my-app - - - Begin loop 192.168.1.22 Jun 02 18:31:42 1 kern err - my-device my-app - - - This is error message no. 2 192.168.1.22 Jun 02 18:31:42 1 kern info - my-device my-app - - - This is info message no. 2 192.168.1.22 Jun 02 18:31:42 1 daemon info - my-device my-app - - - This is daemon info message no. 2 192.168.1.22 Jun 02 18:31:42 1 kern info - my-device my-app - - - End loop 192.168.1.22 Jun 02 18:31:52 1 kern info - my-device my-app - - - Begin loop 192.168.1.22 Jun 02 18:31:52 1 kern err - my-device my-app - - - This is error message no. 3 192.168.1.22 Jun 02 18:31:52 1 kern info - my-device my-app - - - This is info message no. 3 192.168.1.22 Jun 02 18:31:52 1 daemon info - my-device my-app - - - This is daemon info message no. 3 192.168.1.22 Jun 02 18:31:52 1 kern info - my-device my-app - - - End loop
The text was updated successfully, but these errors were encountered:
Using the example code (SimpleLoggingESP8266) running on an ESP32 and either Visual Syslog Server and tftpd64 on windows the first message I actually receive is "This is info message no. 1". This skips over the first 2 messages however after the first loop all messages are sent.
Anyone have any idea why this happens, I have tried adding a large delay and several messages in setup yet no change.
192.168.1.22 Jun 02 18:31:33 1 kern info - my-device my-app - - - This is info message no. 1 192.168.1.22 Jun 02 18:31:33 1 daemon info - my-device my-app - - - This is daemon info message no. 1 192.168.1.22 Jun 02 18:31:33 1 kern info - my-device my-app - - - End loop 192.168.1.22 Jun 02 18:31:42 1 kern info - my-device my-app - - - Begin loop 192.168.1.22 Jun 02 18:31:42 1 kern err - my-device my-app - - - This is error message no. 2 192.168.1.22 Jun 02 18:31:42 1 kern info - my-device my-app - - - This is info message no. 2 192.168.1.22 Jun 02 18:31:42 1 daemon info - my-device my-app - - - This is daemon info message no. 2 192.168.1.22 Jun 02 18:31:42 1 kern info - my-device my-app - - - End loop 192.168.1.22 Jun 02 18:31:52 1 kern info - my-device my-app - - - Begin loop 192.168.1.22 Jun 02 18:31:52 1 kern err - my-device my-app - - - This is error message no. 3 192.168.1.22 Jun 02 18:31:52 1 kern info - my-device my-app - - - This is info message no. 3 192.168.1.22 Jun 02 18:31:52 1 daemon info - my-device my-app - - - This is daemon info message no. 3 192.168.1.22 Jun 02 18:31:52 1 kern info - my-device my-app - - - End loop
The text was updated successfully, but these errors were encountered: