# Did Logstash 1.5.3 version is compatible with Solaris 11.3 version

**URL:** <https://discuss.elastic.co/t/did-logstash-1-5-3-version-is-compatible-with-solaris-11-3-version/99352>\
**Category:** Logstash\
**Created:** [September 5, 2017, 3:18am UTC](https://discuss.elastic.co/t/did-logstash-1-5-3-version-is-compatible-with-solaris-11-3-version/99352 "2017-09-05T03:18:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![yogeswararao](https://avatars.discourse-cdn.com/v4/letter/y/85e7bf/32.png) [@yogeswararao](https://discuss.elastic.co/u/yogeswararao)\
**Post date:** [September 5, 2017, 3:18am UTC](https://discuss.elastic.co/t/did-logstash-1-5-3-version-is-compatible-with-solaris-11-3-version/99352/1 "2017-09-05T03:18:50Z")

</div>

The logstash 1.5.3 version is working fine in the Solaris 10.x version.  
After OS version migrated to 11.3 we are not able to start the logstash service?

which version of Logstah can be used on Solaris 11.3 - it has to output lumberjack to Logstash 1.4.2 (server side)?

I see there is some issue in the ruby script setting up the environment details:  
/apps/apache/logstash-1.5.3/lib/bootstrap/environment.rb ,bundler.rb

when I have checked with logstash 2.3 and logstash 5.4 ,I see same issue?

could you one suggest regarding this issue?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [September 5, 2017, 5:48am UTC](https://discuss.elastic.co/t/did-logstash-1-5-3-version-is-compatible-with-solaris-11-3-version/99352/2 "2017-09-05T05:48:34Z")

</div>

> I see there is some issue in the ruby script setting up the environment details:

Show the full error message.

---

<div class="post-metadata">

**Author:** ![yogeswararao](https://avatars.discourse-cdn.com/v4/letter/y/85e7bf/32.png) [@yogeswararao](https://discuss.elastic.co/u/yogeswararao)\
**Post date:** [September 5, 2017, 1:34pm UTC](https://discuss.elastic.co/t/did-logstash-1-5-3-version-is-compatible-with-solaris-11-3-version/99352/3 "2017-09-05T13:34:26Z")

</div>

Hi Mangus,

Thanks for looking into the issue.

Here is the exception message when I am debugging through the echo statement in servers.

Please let me know in case of any details need.

TypeError: can't convert nil into String  
join at org/jruby/RubyFile.java:1962  
join at org/jruby/RubyFile.java:858  
logstash\_gem\_home at /apps/apache/logstash-1.5.3/lib/bootstrap/environment.rb:40  
setup! at /apps/apache/logstash-1.5.3/lib/bootstrap/bundler.rb:38  
(root) at /apps/apache/logstash-1.5.3/lib/bootstrap/environment.rb:51

Regards,  
Yogesh

---

<div class="post-metadata">

**Author:** ![yogeswararao](https://avatars.discourse-cdn.com/v4/letter/y/85e7bf/32.png) [@yogeswararao](https://discuss.elastic.co/u/yogeswararao)\
**Post date:** [September 8, 2017, 9:57pm UTC](https://discuss.elastic.co/t/did-logstash-1-5-3-version-is-compatible-with-solaris-11-3-version/99352/4 "2017-09-08T21:57:41Z")

</div>

Magnus / ES Team,

is there any update on this request ?

Regards,  
Yogesh

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [September 11, 2017, 6:08am UTC](https://discuss.elastic.co/t/did-logstash-1-5-3-version-is-compatible-with-solaris-11-3-version/99352/5 "2017-09-11T06:08:47Z")

</div>

No, I don't know what's up.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 9, 2017, 6:09am UTC](https://discuss.elastic.co/t/did-logstash-1-5-3-version-is-compatible-with-solaris-11-3-version/99352/6 "2017-10-09T06:09:08Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
