<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:12:33 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-1329] Missing modules on folio-snapshot-283</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1329</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;Something is badly wrong with &lt;a href=&quot;http://folio-snapshot-283.aws.indexdata.com:9130&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://folio-snapshot-283.aws.indexdata.com:9130&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
        <key id="80682">FOLIO-1329</key>
            <summary>Missing modules on folio-snapshot-283</summary>
                <type id="10001" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium">Bug</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="712020:38d1a08f-86a8-4df2-9191-239b16b0a81a">Heikki Levanto</assignee>
                                                                <reporter accountid="712020:38d1a08f-86a8-4df2-9191-239b16b0a81a">Heikki Levanto</reporter>
                                    <labels>
                            <label>core</label>
                            <label>sprint41</label>
                            <label>sprint42</label>
                    </labels>
                <created>Fri, 6 Jul 2018 13:21:05 +0000</created>
                <updated>Mon, 12 Nov 2018 14:24:48 +0000</updated>
                            <resolved>Wed, 11 Jul 2018 09:13:09 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                <comments>
                                                            <comment id="194050" author="712020:38d1a08f-86a8-4df2-9191-239b16b0a81a" created="Fri, 6 Jul 2018 13:23:14 +0000"  >&lt;p&gt;To summarize our discussion on slack:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Cate could not log in to snapshot-stable&lt;/li&gt;
	&lt;li&gt;Marc noticed that mod-users-bl is not enabled for diku&lt;/li&gt;
	&lt;li&gt;Re-enabling the module manually made login work again&lt;/li&gt;
	&lt;li&gt;We proceeded to investigate the situation with curl, for example:   curl -w&apos;\n&apos; &lt;a href=&quot;http://folio-snapshot-283.aws.indexdata.com:9130/_/proxy/modules&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;http://folio-snapshot-283.aws.indexdata.com:9130/_/proxy/modules&lt;/a&gt;&lt;/li&gt;
	&lt;li&gt;We found that there are 11 tenants, diku, supertenant, and 9 from various pull requests&lt;/li&gt;
	&lt;li&gt;They all have a different set of modules enabled.&lt;/li&gt;
	&lt;li&gt;Total 206 enabled modules, with db.maxPoolSize=5 gets us very close to PG&apos;s limit of 1000 connections.&lt;/li&gt;
	&lt;li&gt;diku should have something like 40 modules enabled, but only has 32: These seem to be missing: folio_organization, folio_search, folio_stripes-core, folio_stripes-smart-components, mod-finance, mod-graphql, mod-user-import, okapi, and the mod-users-bl that Marc added manually&lt;/li&gt;
	&lt;li&gt;Nobody seems to know how to get to the logs of that box. Waiting got Malc to come on line.&lt;/li&gt;
	&lt;li&gt;Yesterday we had different problems with the same box, some modules were not running at all.&lt;/li&gt;
	&lt;li&gt;I could not find any dependency problems on the modules enabled for various tenants.  mod-users-bl is required by stripes-core, but that is also not enabled for diku.&lt;/li&gt;
&lt;/ul&gt;

</comment>
                                                            <comment id="194055" author="712020:38d1a08f-86a8-4df2-9191-239b16b0a81a" created="Fri, 6 Jul 2018 13:30:18 +0000"  >&lt;p&gt;Loose theories about what might be behind this:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Out of memory, killed some processes yesterday, and the rest is follow-up problems&lt;/li&gt;
	&lt;li&gt;Out of database handles, may have killed some processes and/or messed with enabling the necessary modules for diku&lt;/li&gt;
	&lt;li&gt;A bug in some script that enables modules, and/or in Okapi itself. This is one of the few cases where we actually run multiple tenants on the same box&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;In any case, I would very much like to get ssh access to the box, or at least see Okapi&apos;s log, and /var/log/kern.log, and maybe more.&lt;/p&gt;</comment>
                                                            <comment id="194058" author="712020:38d1a08f-86a8-4df2-9191-239b16b0a81a" created="Fri, 6 Jul 2018 14:16:36 +0000"  >&lt;p&gt;Ok, I got ssh access. First observations:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;The machine has enough memory, has not swapped since last reboot&lt;/li&gt;
	&lt;li&gt;There seems to be enough disk space as well&lt;/li&gt;
	&lt;li&gt;Okapi logs seem to rotate very often, 10 log files, oldest from yesterday, 19 hours old.&lt;/li&gt;
	&lt;li&gt;No signs of priocesses being killed for lack of memory&lt;/li&gt;
&lt;/ul&gt;
</comment>
                                                            <comment id="194060" author="712020:38d1a08f-86a8-4df2-9191-239b16b0a81a" created="Fri, 6 Jul 2018 14:17:43 +0000"  >&lt;p&gt;grepping in the logs shows that someone (or something) has indeed being deleting modules from diku:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;2018-07-06 07:10:23,974 INFO  ProxyContext         758701/proxy REQ 222.29.81.2:49466 supertenant DELETE /_/proxy/tenants/diku/modules/mod-users-bl-3.0.0-SNAPSHOT.17 okapi-2.16.0
2018-07-06 07:11:06,289 INFO  ProxyContext         640025/proxy REQ 222.29.81.2:49586 supertenant DELETE /_/proxy/tenants/diku/modules/mod-users-15.1.0-SNAPSHOT.36 okapi-2.16.0
2018-07-06 07:11:25,945 INFO  ProxyContext         280882/proxy REQ 222.29.81.2:49624 supertenant DELETE /_/proxy/tenants/diku/modules/mod-users-15.1.0-SNAPSHOT.36 okapi-2.16.0
2018-07-06 07:12:09,270 INFO  ProxyContext         444754/proxy REQ 222.29.81.2:49711 supertenant DELETE /_/proxy/tenants/diku/modules/mod-circulation-10.7.0-SNAPSHOT.159 okapi-2.16.0
2018-07-06 07:12:50,382 INFO  ProxyContext         440252/proxy REQ 222.29.81.2:49780 supertenant DELETE /_/proxy/tenants/diku/modules/okapi-2.16.0 okapi-2.16.0
2018-07-06 07:13:00,709 INFO  ProxyContext         523384/proxy REQ 222.29.81.2:49808 supertenant DELETE /_/proxy/tenants/diku/modules/mod-vendors-1.0.1-SNAPSHOT.20 okapi-2.16.0
2018-07-06 07:16:16,820 INFO  ProxyContext         502273/proxy REQ 222.29.81.2:50203 supertenant DELETE /_/proxy/tenants/diku/modules/mod-users-bl-3.0.0-SNAPSHOT.17 okapi-2.16.0
2018-07-06 07:16:34,644 INFO  ProxyContext         212664/proxy REQ 222.29.81.2:50232 supertenant DELETE /_/proxy/tenants/diku/modules/mod-users-15.1.0-SNAPSHOT.36 okapi-2.16.0
2018-07-06 07:16:57,183 INFO  ProxyContext         721562/proxy REQ 222.29.81.2:50290 supertenant DELETE /_/proxy/tenants/diku/modules/folio_inventory-1.0.3000202 okapi-2.16.0
2018-07-06 07:17:27,530 INFO  ProxyContext         877069/proxy REQ 222.29.81.2:50339 supertenant DELETE /_/proxy/tenants/diku/modules/folio_organization-2.2.100085 okapi-2.16.0
2018-07-06 07:17:57,615 INFO  ProxyContext         476217/proxy REQ 222.29.81.2:50395 supertenant DELETE /_/proxy/tenants/diku/modules/mod-users-bl-3.0.0-SNAPSHOT.17 okapi-2.16.0
2018-07-06 07:18:16,390 INFO  ProxyContext         685537/proxy REQ 222.29.81.2:50428 supertenant DELETE /_/proxy/tenants/diku/modules/folio_stripes-core-2.10.2000301 okapi-2.16.0
2018-07-06 07:18:30,217 INFO  ProxyContext         352045/proxy REQ 222.29.81.2:50444 supertenant DELETE /_/proxy/tenants/diku/modules/folio_stripes-smart-components-1.4.18000201 okapi-2.16.0
2018-07-06 07:18:43,544 INFO  ProxyContext         765735/proxy REQ 222.29.81.2:50475 supertenant DELETE /_/proxy/tenants/diku/modules/mod-vendors-1.0.1-SNAPSHOT.20 okapi-2.16.0
2018-07-06 07:19:06,439 INFO  ProxyContext         058781/proxy REQ 222.29.81.2:50521 supertenant DELETE /_/proxy/tenants/diku/modules/mod-users-bl-3.0.0-SNAPSHOT.17 okapi-2.16.0
2018-07-06 09:50:03,677 INFO  ProxyContext         108587/proxy REQ 31.108.64.95:36353 supertenant POST /_/proxy/tenants/diku/modules okapi-2.16.0
2018-07-06 10:40:33,517 INFO  ProxyContext         621982/proxy REQ 5.57.53.20:48130 supertenant POST /_/proxy/tenants/diku/upgrade okapi-2.16.0
2018-07-06 10:42:12,559 INFO  ProxyContext         950347/proxy REQ 5.57.53.20:48152 supertenant POST /_/proxy/tenants/diku/upgrade okapi-2.16.0
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="194066" author="712020:38d1a08f-86a8-4df2-9191-239b16b0a81a" created="Fri, 6 Jul 2018 14:35:01 +0000"  >&lt;p&gt;whois says that 222.29.81.2 belongs to Peking University.  The timing of the requests seems to indicate manual operations, rather than a script. I think this can explain a lot! I am still not sure if I believe in malicious intent, or simple stupidity...&lt;/p&gt;</comment>
                                                            <comment id="194069" author="557058:4f6bed01-40a6-48d5-8471-7ef21f5ea97c" created="Tue, 10 Jul 2018 14:06:36 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=712020%3A38d1a08f-86a8-4df2-9191-239b16b0a81a&quot; class=&quot;user-hover&quot; rel=&quot;712020:38d1a08f-86a8-4df2-9191-239b16b0a81a&quot; data-account-id=&quot;712020:38d1a08f-86a8-4df2-9191-239b16b0a81a&quot; accountid=&quot;712020:38d1a08f-86a8-4df2-9191-239b16b0a81a&quot; rel=&quot;noreferrer&quot;&gt;Heikki Levanto&lt;/a&gt; I checked with CALIS folks at Beijing. It turns out that an intern was experimenting folio-testing site and did not really know what he was doing. They feel very sorry about that and assure it will not happen again.&lt;/p&gt;</comment>
                                                            <comment id="194071" author="712020:38d1a08f-86a8-4df2-9191-239b16b0a81a" created="Tue, 10 Jul 2018 14:14:29 +0000"  >&lt;p&gt;I figured it was likely to be something like that. In a way, it was a good reminder that we have to use our permission system to secure our publicly visible installations.&lt;/p&gt;
</comment>
                                                            <comment id="194074" author="5bffed52a1b46046f530c8f7" created="Tue, 10 Jul 2018 14:42:12 +0000"  >&lt;p&gt;Yes, this has been a timely wake-up call that has come with relatively little damage.&lt;/p&gt;</comment>
                                                            <comment id="194077" author="712020:38d1a08f-86a8-4df2-9191-239b16b0a81a" created="Wed, 11 Jul 2018 09:13:10 +0000"  >&lt;p&gt;I think we can close this now. The mystery is solved.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzyp7b:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 10 Jul 2018 14:06:36 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>