[Containers] portus not updating dashboard and other stuff

Benjamin Fernandis benjo11111 at gmail.com
Wed Jun 22 18:04:35 MDT 2016


yes , after started portus_crono service, all seems fine and i can see new
pushes and activites on portus.

Can you please point me to delete namespace option as it is feature of new
version

On Wed, Jun 22, 2016 at 10:07 PM, Miquel Sabaté <msabate at suse.com> wrote:

> Hello,
>
> On 06/22/2016 04:52 AM, Benjamin Fernandis wrote:
>
> Hi Miquel,
>
> what i found that after upgrade portus, portus_crono was dead, today i
> started it manually and seems that it fixed problem, Now i can see new push
> on webpage of portus.
>
>
> For the release of Portus 2.1 we are going to take a more serious look at
> upgrading procedures, so these kinds of things don't happen. That being
> said, the portus_crono process exists so it syncs Portus with the registry
> in case that Portus missed events coming from the registry. This means that
> new pushes should've always worked, and in your case it didn't right ? So
> that's weird. Can you see new activities after pushing now then ?
>
>
> In activites dasboard, it only shows major activities , i mean new
> namespace, team etc.. or also shows new tag or image pushed ?
>
>
> It should list all activities, new namespaces, teams, tags, images, etc.
>
>
>
> On Wed, Jun 22, 2016 at 9:54 AM, Benjamin Fernandis <
> <benjo11111 at gmail.com>benjo11111 at gmail.com> wrote:
>
>> Hi Miquel,
>>
>> Previous version : 2.0.1-2.1
>> Current version :  2.0.3-9.2
>>
>> tail -f crono.log
>> Jun 18 13:21:57 portus portus_crono[1185]: I, [2016-06-18T13:13:40.406246
>> #1188]  INFO -- : Perform CatalogJob
>> Jun 18 13:21:57 portus portus_crono[1185]: I, [2016-06-18T13:13:47.982193
>> #1188]  INFO -- : Finished CatalogJob in 7.58 seconds
>> Jun 18 13:21:57 portus portus_crono[1185]: I, [2016-06-18T13:15:40.406864
>> #1188]  INFO -- : Perform CatalogJob
>> Jun 18 13:21:57 portus portus_crono[1185]: I, [2016-06-18T13:15:46.823555
>> #1188]  INFO -- : Finished CatalogJob in 6.42 seconds
>> Jun 18 13:21:57 portus portus_crono[1185]: I, [2016-06-18T13:17:40.407430
>> #1188]  INFO -- : Perform CatalogJob
>> Jun 18 13:21:57 portus portus_crono[1185]: I, [2016-06-18T13:17:46.853558
>> #1188]  INFO -- : Finished CatalogJob in 6.45 seconds
>> Jun 18 13:21:57 portus portus_crono[1185]: I, [2016-06-18T13:19:40.408178
>> #1188]  INFO -- : Perform CatalogJob
>> Jun 18 13:21:57 portus portus_crono[1185]: I, [2016-06-18T13:19:46.993910
>> #1188]  INFO -- : Finished CatalogJob in 6.59 seconds
>> Jun 18 13:21:57 portus portus_crono[1185]: I, [2016-06-18T13:21:40.408801
>> #1188]  INFO -- : Perform CatalogJob
>> Jun 18 13:21:57 portus portus_crono[1185]: I, [2016-06-18T13:21:46.262316
>> #1188]  INFO -- : Finished CatalogJob in 5.85 seconds
>>
>>
>> it shows that after I upgraded portus cronjob is not working
>>
>>  # tail -f production.log
>> I, [2016-06-22T09:44:31.778019 #1543]  INFO -- : Started GET
>> "/namespaces/3" for 10.16.1.30 at 2016-06-22 09:44:31 +1200
>> I, [2016-06-22T09:44:31.779643 #1543]  INFO -- : Processing by
>> NamespacesController#show as HTML
>> I, [2016-06-22T09:44:31.779848 #1543]  INFO -- :   Parameters: {"id"=>"3"}
>> I, [2016-06-22T09:44:31.795560 #1543]  INFO -- :   Rendered
>> namespaces/show.html.slim within layouts/application (8.0ms)
>> I, [2016-06-22T09:44:31.797007 #1543]  INFO -- :   Rendered
>> shared/_header.html.slim (0.8ms)
>> I, [2016-06-22T09:44:31.797800 #1543]  INFO -- :   Rendered
>> shared/_aside.html.slim (0.6ms)
>> I, [2016-06-22T09:44:31.798583 #1543]  INFO -- :   Rendered
>> shared/_notification.html.slim (0.1ms)
>> I, [2016-06-22T09:44:31.798785 #1543]  INFO -- :   Rendered
>> shared/_notification.html.slim (0.0ms)
>> I, [2016-06-22T09:44:31.798884 #1543]  INFO -- :   Rendered
>> shared/_notifications.html.slim (0.9ms)
>> I, [2016-06-22T09:44:31.799142 #1543]  INFO -- : Completed 200 OK in 19ms
>> (Views: 10.5ms | ActiveRecord: 3.1ms)
>>
>>
>> while trying to fetch any error / warn / fatal in production.log, there
>> is no such activity happend.
>>
>>
>> cat /srv/Portus/config/cronotab.rb
>> env = ENV["CATALOG_CRON"] || "5.minutes"
>> Crono.perform(CatalogJob).every eval(env)
>>
>>
>>
>> when we push new images or tag to docker registry it is working fine .
>> portus handle authentication feature. But in portus web interface it is not
>> showing new changes. In dashboard it says last activity happend before 21
>> days.
>>
>>
>> On Tue, Jun 21, 2016 at 10:48 PM, Miquel Sabaté < <msabate at suse.com>
>> msabate at suse.com> wrote:
>>
>>> Hello,
>>>
>>> Since you are using the RPM, could you give us the logs as given by
>>> running the command:
>>>
>>>     $ portusctl logs
>>>
>>> This would help us pin down the problem. You are saying that you
>>> upgraded to 2.0.3, from which version did you upgrade ?
>>>
>>> Cheers,
>>> Miquel
>>>
>>>
>>> On 06/21/2016 02:29 AM, Benjamin Fernandis wrote:
>>>
>>> Hi,
>>>
>>> we noticed that we can not see latest activities on dashboard and while
>>> pushing new versions to namespace, it is not showing and due to that we
>>> upgraded to 2.0.3-9.2 version.
>>>
>>> but still facing same problems. Can you please guide us to resolve this
>>> problem.
>>>
>>> Current Portus info:
>>>
>>> portus:~ # zypper info portus
>>> Retrieving repository 'openSUSE-Leap-42.1-Update' metadata
>>> ........................................................................................................................[done]
>>> Building repository 'openSUSE-Leap-42.1-Update' cache
>>> .............................................................................................................................[done]
>>> Loading repository data...
>>> Reading installed packages...
>>>
>>>
>>> Information for package portus:
>>> -------------------------------
>>> Repository: 2.0.3 Release (openSUSE_Leap_42.1)
>>> Name: portus
>>> Version: 2.0.3-9.2
>>> Arch: x86_64
>>> Vendor: obs://build.opensuse.org/Virtualization
>>> Installed: Yes
>>> Status: up-to-date
>>> Installed Size: 52.6 MiB
>>> Summary: Authorization service and fronted for Docker registry (v2)
>>> Description:
>>>   Portus targets version 2 of the Docker registry API. It aims to act
>>> both as an authoritzation server and as a user interface for the next
>>> generation of the Docker registry.
>>>
>>>   This package has been built with commit 2.0.3 from branch v2.0 on date
>>> Tue, 08 Mar 2016 18:56:49 +0100
>>>
>>>
>>>
>>> _______________________________________________
>>> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>>>
>>>
>>>
>>> _______________________________________________
>>> Containers mailing list
>>> Containers at lists.suse.com
>>> http://lists.suse.com/mailman/listinfo/containers
>>>
>>>
>>
>
>
> _______________________________________________
> Containers mailing listContainers at lists.suse.comhttp://lists.suse.com/mailman/listinfo/containers
>
>
> Cheers,
> Miquel
>
> _______________________________________________
> Containers mailing list
> Containers at lists.suse.com
> http://lists.suse.com/mailman/listinfo/containers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/containers/attachments/20160623/c3085c63/attachment.htm>


More information about the Containers mailing list