node.js - NodeJS: "ENOENT" warning messages with sessions -
i'm using node express-session , session-file-store packages. session data stored files in root directory, using session-file-store package. however, logs being clogged because message [session-file-store] retry, error on last attempt: error: enoent, open 'sessions/_jl2ijmbqhivv8m1mytcnfzgqwgo0t-v.json' appearing 5 times per session cookie accessed in short burst. causing error? it's happening both on windows development machine , on ubuntu server. can't access file apparently, sessions still work.
here 1 of bursts of errors received:
[session-file-store] retry, error on last attempt: error: enoent, open 'sessions/tri6wezeo2uyvr4zaugw6_cu32rjvfpw.json' [session-file-store] retry, error on last attempt: error: enoent, open 'sessions/tri6wezeo2uyvr4zaugw6_cu32rjvfpw.json' [session-file-store] retry, error on last attempt: error: enoent, open 'sessions/tri6wezeo2uyvr4zaugw6_cu32rjvfpw.json' [session-file-store] retry, error on last attempt: error: enoent, open 'sessions/tri6wezeo2uyvr4zaugw6_cu32rjvfpw.json' [session-file-store] retry, error on last attempt: error: enoent, open 'sessions/tri6wezeo2uyvr4zaugw6_cu32rjvfpw.json'
so literally ran same messages when trying first nodejs/express sample project out.
i managed determine @ least in sample project session declared destroyed cookie never cleared, next page loaded used old cookie try , access expired session (already deleted) causing messages logged.
this might not same issue you, figured worth sharing... lazy alternative replace logfn option empty function:
new filestore({logfn: function(){}})
Comments
Post a Comment