Jump to content

Help

LillthNightSide

By LillthNightSide,
in Second Life Viewer

 Share
You are about to reply to a thread that has been inactive for 117 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

LillthNightSide

LillthNightSide

Posted
Posted

everytime i use Firestorm i get this message :

Error:

We're having trouble connecting. There may be a problem with your internet connection or the Second Life Grid.You can either check your internet connection and try again in a few minutes, click help to view the Second Life Support Portal, or click teleport to attempt to teleport home.

internets fine 

Link to comment
Share on other sites
Henri Beauchamp

Henri Beauchamp

Posted
Posted (edited)
6 hours ago, LillthNightSide said:

okay  i have the log file up what am i looking for now?

Look at the ”WARNING” message lines, starting from the end of the log file: anything about the network, the inventory, for example ?...

Also, providing the log file as an attachment to a FS' JIRA would allow FS devels to better/faster diagnose any specific bug.

Oh, and by the way, my link to find the logs in my former message did not really apply to FS (which uses a custom folder for logs instead of LL's viewer standard log folder). See this article about where to find FS' logs.

Edited by Henri Beauchamp
Link to comment
Share on other sites
LillthNightSide

LillthNightSide

Posted
  • Author
Posted (edited)

i was looking in the Wrong place here is the FireStorm Stuff

2023-12-06T23:21:07Z WARNING #Settings# llxml/llcontrol.cpp(1102) LLControlGroup::loadFromFile : Cannot find file C:\Users\Amdin\AppData\Roaming\Firestorm_x64\user_settings\fsdata_defaults.6.6.16.xml to load.

2023-12-06T23:21:14Z WARNING #Settings# llxml/llcontrol.cpp(1102) LLControlGroup::loadFromFile : Cannot find file C:\Program Files\Firestorm-Releasex64\app_settings\account_settings_firestorm.xml to load.

2023-12-06T23:21:15Z WARNING #Settings# newview/llappviewer.cpp(2796) LLAppViewer::loadSettingsFromDirectory : No matching settings group for name Skinning

2023-12-06T23:21:15Z WARNING #Settings# llxml/llcontrol.cpp(1102) LLControlGroup::loadFromFile : Cannot find file C:\Program Files\Firestorm-Releasex64\skins\starlightcui\settings.xml to load.

 

2023-12-06T23:21:23Z WARNING # llui/lluicolortable.cpp(166) LLUIColorTable::insertFromParams : TextEmbeddedItemReadOnlyColor references a non-existent color: EmphasisColor35
2023-12-06T23:21:25Z WARNING # llui/lluicolortable.cpp(166) LLUIColorTable::insertFromParams : TextEmbeddedItemReadOnlyColor references a non-existent color: EmphasisColor35

 

2023-12-06T23:23:49Z WARNING # llwindow/lldxhardware.cpp(796) LLDXHardware::getInfo : szDeviceID000000DC1B59CCF0

2023-12-06T23:24:05Z WARNING #RenderInit# llrender/llgl.cpp(509) LLGLManager::initWGL : No ARB WGL render texture extensions

 

2023-12-06T23:24:05Z WARNING #RenderInit# llrender/llgl.cpp(687) LLGLManager::initGL : VRAM Detected (NVXMemInfo):2048

2023-12-06T23:24:54Z WARNING #ThreadPool# llcommon/llthreadsafequeue.h(314) LLThreadSafeQueue<struct tagMSG,class std::queue<struct tagMSG,class std::deque<struct tagMSG,class std::allocator<struct tagMSG> > > >::push_ : ONCE: Threadsafe queue push_(lockacquired) queue full 1024 >= 1024
2023-12-06T23:25:00Z WARNING #ThreadPool# llcommon/llthreadsafequeue.h(314) LLThreadSafeQueue<struct tagMSG,class std::queue<struct tagMSG,class std::deque<struct tagMSG,class std::allocator<struct tagMSG> > > >::push_ : ONCE (10th time seen): Threadsafe queue push_(lockacquired) queue full 1024 >= 1024
2023-12-06T23:25:30Z WARNING #ThreadPool# llcommon/llthreadsafequeue.h(314) LLThreadSafeQueue<struct tagMSG,class std::queue<struct tagMSG,class std::deque<struct tagMSG,class std::allocator<struct tagMSG> > > >::push_ : ONCE (50th time seen): Threadsafe queue push_(lockacquired) queue full 1024 >= 1024
2023-12-06T23:26:16Z WARNING #ThreadPool# llcommon/llthreadsafequeue.h(314) LLThreadSafeQueue<struct tagMSG,class std::queue<struct tagMSG,class std::deque<struct tagMSG,class std::allocator<struct tagMSG> > > >::push_ : ONCE (100th time seen): Threadsafe queue push_(lockacquired) queue full 1024 >= 1024

 

2023-12-06T23:27:22Z WARNING #ThreadPool# llcommon/llthreadsafequeue.h(314) LLThreadSafeQueue<struct tagMSG,class std::queue<struct tagMSG,class std::deque<struct tagMSG,class std::allocator<struct tagMSG> > > >::push_ : ONCE (200th time seen): Threadsafe queue push_(lockacquired) queue full 1024 >= 1024

2023-12-06T23:28:23Z WARNING #SECAPI# newview/llsecapi.cpp(186) LLCertException::LLCertException : Certificate Error: CertExpired
2023-12-06T23:28:24Z WARNING #ThreadPool# llcommon/llthreadsafequeue.h(314) LLThreadSafeQueue<struct tagMSG,class std::queue<struct tagMSG,class std::deque<struct tagMSG,class std::allocator<struct tagMSG> > > >::push_ : ONCE (300th time seen): Threadsafe queue push_(lockacquired) queue full 1024 >= 1024
2023-12-06T23:28:25Z WARNING #SECAPI# newview/llsecapi.cpp(186) LLCertException::LLCertException : Certificate Error: CertExpired
2023-12-06T23:28:29Z WARNING #SECAPI# newview/llsecapi.cpp(186) LLCertException::LLCertException : Certificate Error: CertExpired
2023-12-06T23:28:34Z WARNING #SECAPI# newview/llsecapi.cpp(186) LLCertException::LLCertException : Certificate Error: CertExpired
2023-12-06T23:28:36Z WARNING #SECAPI# newview/llsecapi.cpp(186) LLCertException::LLCertException : Certificate Error: CertExpired

2023-12-06T23:29:28Z WARNING #ThreadPool# llcommon/llthreadsafequeue.h(314) LLThreadSafeQueue<struct tagMSG,class std::queue<struct tagMSG,class std::deque<struct tagMSG,class std::allocator<struct tagMSG> > > >::push_ : ONCE (400th time seen): Threadsafe queue push_(lockacquired) queue full 1024 >= 1024

2023-12-06T23:30:21Z WARNING #CoreHTTP# llmessage/llcorehttputil.cpp(282) LLCoreHttpUtil::HttpCoroHandler::onCompleted : Possible failure [Http_304] cannot GET url 'http://phoenixviewer.com/app/client_tags/client_list_v2.xml' because Not Modified

2023-12-06T23:30:14Z WARNING #CoreHttp# llcorehttp/_httppolicy.cpp(434) LLCore::HttpPolicy::stageAfterCompletion : HTTP request 000002C5C22F4DA0 failed after 0 retries.  Reason:  Forbidden (Http_403)
2023-12-06T23:30:14Z WARNING #CoreHttp# llcorehttp/_httppolicy.cpp(434) LLCore::HttpPolicy::stageAfterCompletion : HTTP request 000002C5C22F73E0 failed after 0 retries.  Reason:  Not Modified (Http_304)
2023-12-06T23:30:14Z WARNING #CoreHttp# llcorehttp/_httppolicy.cpp(434) LLCore::HttpPolicy::stageAfterCompletion : HTTP request 000002C5C22FAF60 failed after 0 retries.  Reason:  Not Modified (Http_304)
2023-12-06T23:30:14Z WARNING #CoreHTTP# llmessage/llcorehttputil.cpp(282) LLCoreHttpUtil::HttpCoroHandler::onCompleted : Possible failure [Http_304] cannot GET url 'http://phoenixviewer.com/app/fsdata/data.xml' because Not Modified
2023-12-06T23:30:14Z WARNING #CoreHTTP# llmessage/llcorehttputil.cpp(282) LLCoreHttpUtil::HttpCoroHandler::onCompleted : Possible failure [Http_403] cannot GET url 'http://phoenixviewer.com/app/fsdata/defaults.6.6.16.xml' because Forbidden
2023-12-06T23:30:14Z WARNING #CoreHTTP# llmessage/llcorehttputil.cpp(282) LLCoreHttpUtil::HttpCoroHandler::onCompleted : Possible failure [Http_304] cannot GET url 'http://phoenixviewer.com/app/fsdata/grids.xml' because Not Modified

2023-12-07T01:01:47Z WARNING #ThreadPool# llcommon/llthreadsafequeue.h(314) LLThreadSafeQueue<struct tagMSG,class std::queue<struct tagMSG,class std::deque<struct tagMSG,class std::allocator<struct tagMSG> > > >::push_ : ONCE (8400th time seen): Threadsafe queue push_(lockacquired) queue full 1024 >= 1024

Edited by LillthNightSide
Link to comment
Share on other sites
Qie Niangao

Qie Niangao

Posted
Posted
13 minutes ago, LillthNightSide said:

2023-12-04T05:21:24Z WARNING #LLFile# llcommon/llfile.cpp(128) warnif : Couldn't remove 'C:\\Users\\     \\AppData\\Local\\SecondLife\\ba2a564a-f0f1-4b82-9c61-b7520bfcd09f.inv.llsd.gz' (errno 2): No such file or directory

2023-12-04T05:21:24Z WARNING #LLFile# llcommon/llfile.cpp(128) warnif : Couldn't remove 'C:\\Users\\     \\AppData\\Local\\SecondLife\\ba2a564a-f0f1-4b82-9c61-b7520bfcd09f.inv.llsd.gz' (errno 2): No such file or directory

Those "SecondLife" directory tokens seem to suggest this may be a log from the Linden viewer instead of Firestorm. Henri noted in his second post:

9 hours ago, Henri Beauchamp said:

Oh, and by the way, my link to find the logs in my former message did not really apply to FS (which uses a custom folder for logs instead of LL's viewer standard log folder). See this article about where to find FS' logs.

(but if you already followed that and got a logfile with those warnings, please ignore this: it is very possible I'm just confused.)

I also agree with Henri that getting Firestorm developer eyes on that logfile is your best bet at this point, in light of the fact the problem doesn't arise in the Linden viewer—which frankly was not what I expected when I asked earlier.

Link to comment
Share on other sites
Henri Beauchamp

Henri Beauchamp

Posted
Posted

The full LLThreadSafeQueue warnings seem highly suspicious to me, and could possibly be a factor in the login failure.

The CertExpired error could also be relevant: if the viewer fails to negotiate a valid certificate for TLS transactions with the SL sim servers, you won't get in...

Your best bet is to poke FS' support team and file a JIRA, providing the full log as an attachment to the JIRA issue.

Link to comment
Share on other sites
  • Lindens
Monty Linden

Monty Linden

Posted
  • Lindens
Posted
6 hours ago, Henri Beauchamp said:

The CertExpired error could also be relevant: if the viewer fails to negotiate a valid certificate for TLS transactions with the SL sim servers, you won't get in...

May be expected.  SL viewer is shipping five or so expired certs right now.  2025 is when the magic cert expires and that will be an interesting day.

  • Thanks 1
  • Haha 1
Link to comment
Share on other sites
EnCore Mayne

EnCore Mayne

Posted
Posted

i asked FS support about my own certificate warnings:

found these warnings in the Firestorm.log

WARNING #SECAPI# newview/llsecapi.cpp(186) LLCertException::LLCertException : Certificate Error: CertExpired
WARNING #SECAPI# newview/llsecapi.cpp(186) LLCertException::LLCertException : Certificate Error: CertExpired
WARNING #SECAPI# newview/llsecapi.cpp(186) LLCertException::LLCertException : Certificate Error: CertExpired
WARNING #SECAPI# newview/llsecapi.cpp(186) LLCertException::LLCertException : Certificate Error: CertExpired
WARNING #SECAPI# newview/llsecapi.cpp(186) LLCertException::LLCertException : Certificate Error: CertExpired

any cause for concern?

 

 

 

 

 

 

 

 

 

 

the FS dev's answer was: "Nope. And it would be LL's job anyway."

i'm one version back from their newest so maybe they're caught up. who knows. the log indicated the "Certificate store" CA.pem wasn't in my user settings and since it wasn't isn't there it reverted to the FS root's ca-bundle.crt where the warnings above came back.

INFO from llsechandler_basic.cpp(637) says: loaded 129 good certificates (rejected 5) from C:\Program Files\Firestorm-Releasex64\ca-bundle.crt.

that's a pretty good average : ) everything runs fine (as far as i know) without having those 5 rejects.

Link to comment
Share on other sites
Qie Niangao

Qie Niangao

Posted
Posted
42 minutes ago, Alwin Alcott said:

a jira never helps it''s to bring issues to the attention of the developer.

I'm not sure how Firestorm operates, but their support page specifically links to their Jira for filing support tickets:

Quote
  • File a support ticket or bug report on our JIRA. Best option for help if your issue isn’t time-sensitive (response times may be slow), if you can’t log in or stay logged in to Second Life, or if your issue may be a bug in the viewer’s code that can only be fixed by a developer. If you need immediate assistance and can log in, even if it’s only on an alt or a different viewer, then the inworld support groups below are a better choice.

but also, yeah, because the OP can login (albeit from the Linden viewer) it might be worth trying one of their inworld support groups listed on that support page. Or check their wiki, also suggested there, for any relevant hints.

Link to comment
Share on other sites
  • 3 weeks later...
  • 3 weeks later...
You are about to reply to a thread that has been inactive for 117 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...