Log in to create and rate content, and to follow, bookmark, and share content with other members. Not a member? Join Now!

AnsweredAssumed Answered

Two issues that may be related...

Question asked by jesse.tushinsky on Apr 4, 2018
Latest reply on Apr 4, 2018 by wimdecorte

Like • Show 0 Likes0
Comment • 10

1) All web UI users get logged off automatically when idle for anytime between 15-25 minutes despite the time being set to 60 minutes. This only happens for web users

2) The web hosting server will intermittently crash without warning. The only resolution, other than rebooting the computer running FMS, is to click through the server setup again.

This happens on two different FM Server machines on two different networks, both having clean Mac OS 10.12 installs prior to setting up FMS.

We need help! Thanks

No one else has this question

Outcomes

10 Replies

mikebeargie Apr 4, 2018 10:04 AM
Mark Correct
Correct Answer
what version of filemaker server?
what exact installer are you using?
what timeout settings do you have in the user privilege sets?
what timeout settings do you have in the filemaker server admin console?
Like • Show 0 Likes0
Actions
wimdecorte Apr 4, 2018 10:10 AM
Mark Correct
Correct Answer
2) The web hosting server will intermittently crash without warning
Describe that in some more detail? Do you get actual crash reports? Or is it more that it stops responding?
And it sounds like this is a two-machine setup? With FMS on one machine and the web server on another. Is this WebDirect or a custom web publishing application?
Like • Show 0 Likes0
Actions
jesse.tushinsky @ mikebeargie on Apr 4, 2018 10:18 AM
Mark Correct
Correct Answer
Thanks for chiming in.

what version of filemaker server?
• v16.0.3.304
what exact installer are you using?
• We used the installer provided by our sales rep at the time of purchase (16.0.2) and then updated when the current version was released.
what timeout settings do you have in the user privilege sets?
• We have a dozen databases, all with the same issue. But, we have the two user groups in use (both external server) set to not logout when idle.
what timeout settings do you have in the filemaker server admin console?
• Web Direct session timeout settings are at 60 minutes

Hope that info helps.
Like • Show 0 Likes0
Actions
jesse.tushinsky @ wimdecorte on Apr 4, 2018 10:30 AM
Mark Correct
Correct Answer
Thanks for your response.

We have a single machine setup and running FileMaker Server. It handles the storage of all the databases, backups, and web hosting (WebDirect). We have dozens of users accessing these databases at any given time. They connect using the web interface and login using Active Directory credentials (setup as an external server group in each databases' user settings). When idle for 15-25 minutes (the time range varies depending on browser), they are logged out. It is important to note that the WebDirect timeout setting on FMS is set to the max of 60 minutes. That's the first issue. The second is the WebDirect feature as a whole. At any given time, without warning, WebDirect will stop working. Only editing deployment brings it back online. The logs show nothing.

Hope that helps
Like • Show 0 Likes0
Actions
wimdecorte @ jesse.tushinsky on Apr 4, 2018 10:53 AM
Mark Correct
Correct Answer
What's the spec on the server?

Does the FMS event log the disconnect of the users? ("Not responding" warnings for instance)
Like • Show 0 Likes0
Actions
jesse.tushinsky @ wimdecorte on Apr 4, 2018 11:08 AM
Mark Correct
Correct Answer
The server computer is a 2012 Mac Pro running OS 10.12.6 with 2x 2.4GHz Quad core procs, 32GB RAM, a 512GB SSD for OS, and 512GB RAID1 made from 2 SSDs for the databases.

The event log does show users being disconnected; says their connection was closed.
Like • Show 0 Likes0
Actions
wimdecorte @ jesse.tushinsky on Apr 4, 2018 11:23 AM
Mark Correct
Correct Answer
Ok, not bad specs. The machine is fairly old so it could be a NIC hardware issue. Or it could be an upstream issue on the network. The fact that the log shows that the users were disconnected and their connection does indicate some sort of network issue somewhere. FMS has not been able to maintain the heartbeat to the webdirect user.

If you haven't already: turn on the stats.log, clientstats.log and topcallstats.log to collect more information on how the server is behaving.
Like • Show 0 Likes0
Actions
wimdecorte @ jesse.tushinsky on Apr 4, 2018 11:24 AM
Mark Correct
Correct Answer
jesse.tushinsky wrote:
We have dozens of users accessing these databases at any given time.

How many peak? Dozens is too vague. Since you have everything on one machine and are using older processors, knowing the peak load and the numbers from the stats.log could be crucial.
Like • Show 0 Likes0
Actions
jesse.tushinsky @ wimdecorte on Apr 4, 2018 12:29 PM
Mark Correct
Correct Answer
"If you haven't already: turn on the stats.log, clientstats.log and topcallstats.log to collect more information on how the server is behaving."
• Thank for that. How would I go about turning those on?

"How many peak? Dozens is too vague. Since you have everything on one machine and are using older processors, knowing the peak load and the numbers from the stats.log could be crucial."
• No more than 45 users at the same time (license limit, that we stay closing to hitting during peak).
Like • Show 0 Likes0
Actions
wimdecorte @ jesse.tushinsky on Apr 4, 2018 12:46 PM
Mark Correct
Correct Answer
45 users, most of them on WebD on an 8-core machine (~16 if HyperThreading): I'd be interested to see what stats you get out of it.

Here's how you toggle them on; note that the bottom two turn themselves off every time you restart FMS so you have to remember to turn them back on.
Like • Show 0 Likes0
Actions

Two issues that may be related...

Outcomes

Related Content

Recommended Content